Chapter 3. MTA 7.2.2

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)