Before this update, the analysis performance for Java binaries degraded because MTA relied on Maven search to analyze Java binary applications. With this enhancement, MTA has pre-generated bundled Maven index that does not require connecting to an external index through a network connection. As a result, MTA performs fast, low-memory look-ups of Maven artifacts by using local Maven Search and you can analyze Java binaries in disconnected environments.

MTA-6231

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-6262

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-6211

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. As a result, the discovery fails.

To work around this problem, run the application discovery by using the MTA command-line interface (CLI).

MTA-6424

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)

does not match

 String str = "something";
 Servlet s = exception1.getServlet();
 UnavailableException exception2 = new UnavailableException(s, str);

In addition, search patterns that do not contain Fully Qualified Names (FQNs) do not match. For example:

    java.referenced:
      location: CONSTRUCTOR_CALL
      pattern: UnavailableException(Servlet s,String str)

No known workaround exists.

MTA-6402

When you analyzed Java binary applications, MTA incorrectly classified some open source dependencies as internal dependencies. With this version, MTA classifies embedded open source dependencies correctly after a source+dependency binary analysis.

MTA-6357

When you imported applications from Cloud Foundry (CF), MTA did not have a provision for you to mention the CF organizations. With this release, 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-6271

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, MTA CLI successfully completes the discovery of CF applications with service bindings.

MTA-6399

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, you no longer have to manually add the Cloud Foundry tag in the imported application.

MTA-6282

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, Architects can import CF applications in the Application Inventory.

MTA-6120

Concurrent usage of the Solution Server through the Red Hat Developer Lightspeed for MTA in Visual Studio Code for code resolution at scale caused race conditions for duplicate incidents. With this release, the plugin generates resolutions for the incidents identified when many users use it concurrently.

MTA-6230

Before this update, the annotation rules for Java applications did not use Fully Qualified Names (FQNs) to match with the annotation location in source code. 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, MTA uses the FQN in the ANNOTATION field in rules to match annotations in the source code.

MTA-6195

MTA did not trigger rules to match import statements that contain a wildcard when analyzing a Java application. As a result, MTA did not detect specific incidents in the report after the analysis. With this release, this issue is fixed.

MTA-4027

When you disabled the Allow insecure connection for an application stored in the Subversion (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, you can edit secure SVN applications in the MTA user interface.

MTA-6263

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, you can analyze an application stored in SVN repository without any error.

MTA-6141

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, you can use MTA to run an analysis on the source code even if you do not configure the repository type field.

MTA-6105

Before this update, you could not proceed to the final step after filling in the responses to the custom questionnaire because MTA disabled the Next button in the web console. With this release, you can complete the questionnaire in MTA user interface.

MTA-6143

When you uploaded more than one custom rule at a time in the web console, MTA did not detect the rules. With this version, you can upload one or more custom rules at once.

MTA-6029

You can opt to use Red Hat Developer Lightspeed for MTA features in the Visual Studio Code extension. With the Developer Lightspeed feature, you can use a large language model (LLM) of your choice to request code changes for resolving the issues found through a static code analysis of your Java application.

The Red Hat Developer Lightspeed for MTA core features are the following:

MTA-5371

You can use platform awareness to discover applications from a source platform and import them into the MTA application inventory. MTA discovers the applications by their coordinates on the source platform where you deployed them. With platform awareness, you can use the platform and runtime configurations of applications to create a discovery manifest to generate other deployment assets. In MTA 8.0.0, you can discover applications deployed in the Cloud Foundry platform.

MTA-4846

You can use the discovery manifest to generate assets in the web console to deploy applications in Red Hat OpenShift or Kubernetes. The asset generation workflow includes generators, target profiles, and the archetypes. Generators parse the application manifest configurations to create the deployment assets for a specific kind of target platform. In the target profiles, you can run one or more generators in sequence for a given archetype.

MTA-4847

With this update, you can perform a live discovery to determine applications that you deployed in a certain Cloud Foundry (CF) cluster. For example, you can determine how many applications are in the cluster. You can also use the live discovery if you do not have access to manifest YAML files.

For more information, see Performing a live discovery in a remote CF instance.

MTA-4847

You can conceal sensitive information, for example, services and Docker credentials, in a Cloud Foundry (CF) discovery manifest by using the mta-cli discover cloud-foundry --conceal-sensitive-data command. This command generates the following files:

For more information, see Concealing sensitive information in a discovery manifest.

MTA-4847

Analysis insights contain information about the technologies used in the application and their usage in the code. Before this update, you could only view insights in the analysis output and a static report after running an application analysis. With this enhancement, you can access analysis insights also from the migration toolkit for applications (MTA) user interface (UI).

MTA-5420

With this enhancement, you can use a new Visual Studio Code Integrated Development Environment (IDE) plugin that has the following features:

MTA-5360

Before this update, you could only assign credentials to an application manually after you added or imported this application to the migration toolkit for applications (MTA) user interface (UI). However, you might need to import a large set of applications,with each application requiring credentials for language and technology discovery tasks. With this update, instead of manually defining credentials, you can define default credentials for any application that does not yet have credentials.

For more information, see Setting default credentials.

MTA-5254

Solution Server is a component that allows Developer Lightspeed for MTA to build a collective memory of code changes from all analysis performed in an organization. This capability is a Technology Preview feature. The Solution Server works with the LLM to improve the pattern of resolutions from solved examples for future analysis.

The Solution Server has the following benefits:

In migration toolkit for applications (MTA) 8.1.1, MTA removes XML rules and no longer supports them in the MTA user interface (UI) and command-line interface (CLI).

MTA-5357

An application analysis by using the migration toolkit for applications (MTA) command-line interface (CLI) might fail with the following error message:

level=error msg="initialize failed" error="context canceled" provider=java
error="invalid header line "An error has occurred. See the log file"

To work around this problem, clean up metadata and cache:

MTA-6125

When you use Developer Lightspeed for MTA, the analysis results do not change if you include or remove a custom rule but do not restart the analyzer process.

To work around this problem, restart the analyzer process by clicking the Start/Stop button after making a configuration change.

MTA-6129

The ANNOTATION search location does not properly use Fully Qualified Names (FQNs) to match annotations. This leads to incorrect matches and false positives in analysis issues. For example, a rule that searches for annotations using the javax.enterprise.inject.Produces pattern might incorrectly match the occurrences of the javax.ws.rs.Produces annotation in the source code.

No known workaround exists.

MTA-6195

The Solution Server throws a connection error when concurrent connections increase in a short span of time. To work around this problem, enter the following command to allow the Developer Lightspeed for MTA database to expire idle connections:

oc -n openshift-mta exec deploy/kai-db – psql -U postgres -d postgres -c "ALTER ROLE kai SET idle_session_timeout = '1min'; ALTER ROLE kai SET idle_in_transaction_session_timeout = '1min';"

MTA-6204

Before this update, when you generated a deployment manifest by using the Helm template, MTA ignored the default values in the values.yaml file packaged with the Helm chart. As a result, MTA used only the values from the values.yaml file created after running the mta-cli discover command. With this update, MTA merges the default values.yaml file with the discover values.yaml file.

MTA-5793

Before this update, when you ran an application analysis for Gradle projects in containerless mode, migration toolkit for applications (MTA) command-line interface (CLI) did not detect Gradle dependencies. As a result, the analysis report did not list the dependencies and displayed an error message in the analysis logs instead. With this update, MTA CLI detects Gradle dependencies after the analysis is complete.

MTA-4033

Before this update, when you analyzed an application built with Gradle in Source code + dependencies mode in the migration toolkit for applications (MTA) user interface (UI), the analysis failed if you had Gradle version 7 or later installed. With this update, you can analyze applications built with Gradle 7 or later in the MTA user interface.

MTA-5907

Before this update, the mta-cli discover command only moved an application-level process with the process type explicitly defined to the processes block in the discovery manifest. As a result, the discovery manifest did not list implicit application-level processes in the processes block. This resulted in the violation of the recommended clarity and proper configuration practices, especially if Cloud Foundry application manifest includes multiple process types. With this update, mta-cli discover moves both implicit and explicit application-level process types to the processes block in the discovery manifest.

MTA-6030