Red Hat SummitChapter 1. MTA 8.0.1
The MTA 8.0.1 section lists the fixed issues and known issues.
1.1. Known issues
Migration toolkit for applications (MTA) version 8.0.1 is affected by the following newly identified and previously known issues. A known issue is listed in all future release notes until resolved, at which point it is published as a fixed issue.
MTA assessment form malfunctions when you use it with a custom questionnaire
In the MTA user interface, selecting an answer to a question in the assessment form generated from a custom questionnaire causes the form to select an option available for another question.
To work around this problem, ensure that one or more order keys listed in a section, for example answers, have a unique order number.
MTA UI does not trigger a violation for open source dependencies in Gradle applications
MTA UI does not trigger a violation for open source libraries when you run a source+dependency analysis of a Gradle application. As a result, the analysis report does not list incidents for open source dependencies.
To work around this problem, analyze Gradle applications by using the MTA command-line interface (CLI).
MTA UI fails to process applications with service bindings
When you use the migration toolkit for applications (MTA) user interface (UI) to run an application discovery for a deployed Cloud Foundry (CF) application with a service binding, MTA UI does not parse the VCAP_SERVICES environment variables correctly to handle service binding information. Consequently, the discovery fails.
To work around this problem, run the application discovery by using the MTA command-line interface (CLI).
Rules with METHOD_CALL or CONSTRUCTOR_CALL do not match expected locations when specifying parameters
Search patterns in Java rules that have the METHOD_CALL and CONSTRUCTOR_CALL locations do not match the expected methods and constructors in the application source code.
For example:
java.referenced:
location: CONSTRUCTOR_CALL
pattern: javax.servlet.UnavailableException(javax.servlet.Servlet,java.lang.String)
java.referenced:
location: CONSTRUCTOR_CALL
pattern: javax.servlet.UnavailableException(javax.servlet.Servlet,java.lang.String)does not match
String str = "something"; Servlet s = exception1.getServlet(); UnavailableException exception2 = new UnavailableException(s, str);
String str = "something";
Servlet s = exception1.getServlet();
UnavailableException exception2 = new UnavailableException(s, str);In addition, search patterns that do not contain Fully Qualified Names (FQN) do not match. For example:
java.referenced:
location: CONSTRUCTOR_CALL
pattern: UnavailableException(Servlet s,String str)
java.referenced:
location: CONSTRUCTOR_CALL
pattern: UnavailableException(Servlet s,String str)No known workaround exists.
1.2. Fixed issues
Migration toolkit for applications (MTA) version 8.0.1 provides the following fixed issues and other problems that have a significant impact.
In MTA 8.0.1 the performance of Java binary analysis has significantly improved. Before this change, when you analyzed Java binary applications, MTA incorrectly classified some open-source dependencies as internal dependencies, it was then decompiled and analyzed, that caused the analysis to take longer to complete. Now, the location of the Maven index file is passed to the Java provider to determine if an embedded dependency is open-source or internal. This fix resolved the two following issues:
Binary application analysis latency is reduced in MTA
When you analyzed a binary, the performance degraded because MTA relied on Maven search. With this release, this issue is fixed by introducing the pre-generated Maven index that does not require connecting to an external index.
Analysis of binary applications classify open source dependencies accurately
When you analyzed Java binary applications, MTA incorrectly classified some open-source dependencies as internal dependencies. With this version, this issue if fixed. This leads to MTA classifying embedded open source dependencies correctly after a source+dependency binary analysis.
MTA enables you to target an organization when importing applications from Cloud Foundry
When you imported applications from Cloud Foundry (CF), MTA did not have a provision for you to mention the CF organizations. With this release, this issue is fixed. You can configure one or more organizations, spaces, and applications for the discovery process. The spaces can belong to different organizations and the applications can belong to different spaces. You must specify at least one organization for application discovery.
MTA CLI correctly processes Cloud Foundry applications with service binding
The discovery process of Cloud Foundry (CF) applications with service bindings by using live connection failed in MTA CLI. The MTA CLI did not parse the VCAP_SERVICES environment variables correctly to handle service binding information for an array of services. For example, cf bind-service <application_name> postgres01. With this version, this issue is fixed. As a result, MTA CLI successfully completes the discovery of CF applications with service bindings.
Cloud Foundry applications imported in MTA are tagged automatically
When you imported applications in MTA from a Cloud Foundry (CF) instance, the applications did not contain the Cloud Foundry tag. The tag links an application to an archetype. The archetype has a generator that produces the deployment assets for a migration path. With this release, this issue is fixed. You no longer have to manually add the Cloud Foundry tag in the imported application.
You can import Cloud Foundry applications from the application inventory in the MTA web console
Before this update, an MTA Architect could not discover or import applications from the Cloud Foundry (CF) source platform on the application inventory page. As a result, only an MTA Administrator could import the applications on the Source platforms page in the Administrator mode. With this release, this issue is fixed. Architects can now import CF applications in the Application Inventory.
Concurrent usage of Red Hat Developer Lightspeed for MTA for code resolution at scale no longer causes race conditions
Concurrent usage of the Solution Server through the Red Hat Developer Lightspeed for MTA Visual Studio (VS) Code plugin for code resolution at scale caused race conditions for duplicate incidents. With this release, this issue is fixed. The plugin generates resolutions for the incidents identified when many users use it concurrently.
MTA rules for Java use FQN to match annotations in source code
Before this update, the annotation rules for Java applications did not use Fully Qualified Names (FQNs) to match with the annotation location in rules. As a result, the rule triggered incorrect matches or false positives for issues. For example, a rule that looked for the javax.enterprise.inject.Produces incorrectly matched with occurrences of javax.ws.rs.Produces. With this release, this issue is fixed.
MTA triggers rules to match import statements with wildcard in Java applications analysis
MTA did not trigger rule to match import statements that contain a wildcard when analyzing a Java application. Consequently, specific incidents were not detected in the report after the analysis. With this release, this issue is fixed.
MTA user interface enables you to edit secure SVN application without an error
When you disabled the Allow insecure connection for an application stored in the SVN repository and edited the application, the user interface displayed a blank page some times with the TypeError cannot read properties of undefined (reading 'kind'). With this version, this issue is fixed. You can edit secure SVN applications in the MTA user interface.
MTA no longer fails language and tech discovery for Java application in SVN repositories
Before this update, for a Java application source code stored in an SVN repository, MTA produced an error when trying to checkout the repository by using the SVN credential. As a result, the language and tech discovery of the application failed. With this release, this issue is fixed. You can now analyze an application stored in SVN repository without any error.
MTA displays source repository URL when you skip configuring the repository type field
MTA did not show the source repository URL in the application details view if you did not select between the Git or Subversion repository type. As a result, you could not run an analysis on the application source code. With this release, this issue is fixed. You can now use MTA to run an analysis on the source code even if you do not configure the repository type field.
You can complete an assessment by using a custom questionnaire in the MTA user interface
Before this update, you could not proceed to the final step after filling in the responses to the custom questionnaire because the Next button was disabled in the web console. With this release, this issue is fixed.
MTA web console detects custom rules when many are uploaded at a time
When you uploaded more than one custom rule at a time in the MTA web console, the rules were not detected. With this version, this issue is fixed. You can upload one or more custom rules at once.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}