Release Notes

MTA creates resources with auto-assigned IDs after creating RESTful resources with specific IDs

Previously in MTA, when a resource was created with a specific ID through a REST call, after which another resource was created with an auto-assigned ID, either through a REST call or in the user interface, an http-409 conflict could occur. This issue has been resolved in MTA 7.2.3. (MTA-5288)

MTA now runs Java rules when analyzing Java binaries on Microsoft Windows

Previously, when you performed a containerless analysis of compiled Java applications using Microsoft Windows, MTA did not match a Java rule and generated a Java Model (code 969) error. As a result, some rules did not trigger issues in the analysis report. This issue has been resolved in MTA 7.2.3. (MTA-5370)

Resources and limits now present on all pods

In MTA 7.2.3, all pods created by the mta-operator and the pod for the operator have resource limits and requests set. This way they also work in an environment where resource limits and requests are required, for example, when a project has resource quotas defined. (MTA-5406)

Running analysis on large .EAR binary filesobtains differents results

When analyzing binary applications, MTA relies on Maven search index to determine whether dependencies are internal to the application or whether the application is installed as an open-source dependency. Depending on the availability of the Maven search index, it is assumed that an open-source dependency is internal to the application and includes the dependency in the analysis results. In this case, analysis returns more incidents and greater effort to address issues found in dependencies, even if the user does not expect to see those results.

MTA CLI generates a process error in log after Java binary analysis using Microsoft Windows

When you analyze Java binaries using Microsoft Windows, MTA CLI generates a process error when deleting files in the exploded directory after moving the decompiled files to the Java project path. This error does not affect the analysis results. Currently, there is no workaround for this issue. (MTA-5355)

MTA CLI analysis can take a long time for multi-module binaries when dependency resolution fails

When you analyze multi-module binaries in MTA CLI, the analysis can take a long time to complete if dependency resolution fails. Currently, there is no workaround for this issue. (MTA-5398)

MTA CLI completes an analysis for compiled Java binary without dependencies

Previously, when analyzing applications that did not include dependencies in the compiled Java binary, MTA CLI failed the analysis because no dependency was found. This issue has been resolved in MTA 7.2.2. (MTA-3415)

MTA CLI allows the use of --target flag for custom targets

Previously, to create a custom target, MTA CLI did not allow the --target flag in analysis. The analysis did not complete even though custom rules were available for the custom target. This issue has been resolved in MTA 7.2.2. (MTA-4629)

MTA CLI analysis generates consistent effort for applications with private repository source control

Previously, in the MTA CLI, repeated analysis of an application with a private repository source control generated varying effort. This issue has been resolved in MTA 7.2.2. (MTA-2984)

Issue report suggests fix for issues after an analysis in the MTA CLI

Previously, the HTML issue report did not describe the fix for issues after completing an analysis in the MTA CLI. This issue has been resolved in MTA 7.2.2. (MTA-4782)

WebLogic application analysis in MTA CLI generates more issues

Previously, the Oracle WebLogic Server rule did not trigger issues for the PromoService class under the proprietary logger category, after analyzing a Java application in the MTA CLI. This issue has been resolved in MTA 7.2.2. (MTA-3845)

Metric target statuses for RHSSO operator are up for Tackle add-on

Previously, when you configured tackle with authentication for the MTA operator, the statuses of Red Hat Single Sign On (RHSSO) operator’s metric targets were down in the OpenShift Container Platform console. This issue has been resolved in MTA 7.2.2. (MTA-4816)

Go targets are displayed in the Application Analysis wizard

Previously, in the Application Analysis tab of the MTA user interface, when users navigate back to the Set Target page where Go was the selected target, the target defaulted to Java. This issue has been resolved in MTA 7.2.2. (MTA-3438)

MTA generates false positive issues in Java application analysis

When you analyze Java applications, MTA rules can trigger a false positive issue by matching the line 1 of a Java file. Currently, there is no workaround for this issue. (MTA-4918)

Source code and dependency analysis of Java applications generate varying effort

When you run multiple source code + dependency repeated analysis of Java applications for the OpenJDK 17 target, MTA generates varying effort. Currently, there is no workaround for this issue. (MTA-4943)

OpenRewrite CMD now properly mounts the settings file

The Migration Toolkit for Applications (MTA) CLI not only analyzes source code but also transforms it to adopt a particular technology. To transform the code, MTA can use an external settings file, for example, to access the Maven repository. In such cases, this file must be mounted to a running container where the analysis engine will run.

The application analysis no longer fails on RHEL 8

Previously, when you ran the application analysis with the MTA 7.2.0 version on RHEL 8 systems, the analysis failed with the version `GLIBC_2.32' not found error. With this update, the issue has been resolved, and the application analysis no longer fails for RHEL 8. (MTA-4634)

Application analysis might fail to resolve dependencies

When you run application analysis by using the MTA user interface (UI) for any target application, the dependencies list might be shown as empty after the analysis is complete. Currently, there is no workaround for this issue. (MTA-4598)

Containerless CLI

You can perform an application analysis for Java applications by using the MTA CLI that does not require installation of a container runtime. For more details, see Running the containerless CLI.

Tags are not accessible in SVN repositories

In previous versions of MTA, when retrieving source code from Subversion (SVN) repositories, addons were automatically adding /trunk or /branches/<target_branch> to the repository URL, making it impossible to check out anything under tags. This issue has been resolved in the MTA 7.2.0. (MTA-4236)

Application import fails when Business Services exist already

In previous versions of MTA, importing applications using a CSV after a previous import that created Business Services led to the newly created applications having the incorrect Business Services assigned. This issue has been resolved in the MTA 7.2.0. (MTA-4257)

MTA CLI fails to handle --bulk properly on Windows platform

In previous versions of MTA, the bulk analysis on Windows systems could not be performed. This issue has been resolved now in the MTA CLI. (MTA-3624)

IntelliJ IDEA target list showed unusable targets

In previous versions of MTA, selecting cloud as a target resulted in an unknown target error. This issue has been resolved in the MTA 7.2.0. (MTA-4035)

Maven insecure setting not functioning as expected

In previous versions of MTA, the global Maven setting to Consume insecure repositories was no longer passed to Maven. As a result, Maven failed when using Hyper Text Transfer Protocol (HTTP) repositories. This failure was a regression bug introduced when the Maven functionality was moved to the Java provider. This issue has been resolved in the MTA 7.2.0. (MTA-4418)

SVN Checkout fails when filenames have special characters

In previous versions of MTA, the Subversion (SVN) client failed when attempting a checkout operation in a repository that contained files with special characters, accents, in their filenames. This issue has been resolved in the MTA 7.2.0. (MTA-4309)

MTA CLI analysis using the CLI in container and containerless modes periodically fails on Windows

MTA [CLI] analysis using the CLI in container and containerless modes periodically fails on Microsoft Windows and returns a provider does not have dependency capability error. This failure is caused by the existence of a corrupted .metadata folder located inside the directory where the analysis is run. Therefore, the workaround is to delete this folder. This issue is planned to be resolved in MTA 7.2.1. (MTA-4410)

MTA CLI analysis is extremely slow on Windows

MTA CLI analysis does not function as expected on Microsoft Windows, with analysis using container runtimes being extremely slow on Windows. This issue is planned to be resolved in MTA 7.2.1. (MTA-3667)

Running analysis of the application in containerless mode fails to fetch some dependencies

Running analysis of the application in containerless mode fails to fetch some dependencies, which is caused by the MTA Operator using Maven 3.6 is failing to fetch dependencies. The workaround is for the user to upgrade to Maven 3.9. This issue is planned to be resolved in MTA 7.2.1. (MTA-4169)

MTA CLI bulk analysis does not function on Windows

MTA CLI bulk analysis, performed by using the --bulk option, does not function on Microsoft Windows. This issue is planned to be resolved in MTA 7.2.1. (MTA-4307)

Binary analysis fails with incorrect Maven credentials

MTA CLI analysis fails with a generic error when incorrect Maven credentials are used. The failure occurs because the analyzer is unable to report detailed error messages. (MTA-3714)

MTA containerless CLI report is inconsistent when analyzing two binary applications located in the same folder

The report generated by containerless CLI analysis is inconsistent when it has analyzed two binary applications that are located in the same folder. This issue is planned to be resolved in MTA 7.2.1. (MTA-4484)

Duplicate entries are appearing because some files inside the target folder are being analyzed

You can see duplicate entries in the built-in provider searches if the application is compiled using the mvn clean package. This issue is planned to be resolved in a later release of MTA. (MTA-4260)

Dependency rule of a custom rules file in analysis is not fired

A custom dependency rule is not fired, and no related migration issue is found. (MTA-3863)

No multi-user access restrictions on resources

There are no multi-user access restrictions on resources. For example, an analyzer task created by a user can be canceled by any other user. (MTA-3819)