Chapter 1. MTA 7.3.2

MTA now generates consistent results after analyzing large .EAR binary files

Previously, when analyzing binary applications, MTA relied on the Maven search index to determine whether embedded dependencies were internal to the application or were publicly available (usually classified as open-source dependency). Depending on the availability of the Maven search index, an open-source dependency could be wrongly classified as internal to the application and was included as a dependency in the analysis results. In this case, the analysis returned more incidents and greater effort to address issues found in dependencies. This issue has been resolved in MTA 7.3.2 by adding the flag --disable-maven-search to the analyze command. When disabled, the analysis will consistently classify dependencies. (MTA-5588)

MTA user interface connection breaks when you sort dependencies by labels after an analysis

When you sort the dependencies by labels after analyzing an application in the MTA user interface, the user interface displays an error about retrieving data. Currently, there is no workaround available. (MTA-5981)

Analysis performance may degrade in a disconnected environment or when Maven central is not available

When you run an analysis by using the MTA on a host with no access to Maven central and without disabling the Maven search index (--disable-maven-search=false), the analysis performance may degrade, as MTA tries to access it.

An application analysis lasts longer when Maven credentials are missing

If you do not manually assign Maven credentials to an application that requires them or do not set these credentials as default, an application analysis might last longer. In addition, the Analyzer and Tech Discovery steps complete with the following error: