Chapter 2. MTA 7.3.2


2.1. Technical changes

The following technical changes have been made in Migration Toolkit for Applications (MTA) 7.3.2:

The Eclipse IDE plug-in is deprecated

The Eclipse IDE plug-in for Migration Toolkit for Applications (MTA) is deprecated and will be removed in a future major release. Red Hat will provide bug fixes and support for this feature during the current release lifecycle, but this feature will no longer receive enhancements.

2.2. Fixed issues

This section provides the following bug fixes and resolved issues that have a significant impact on the Migration Toolkit for Applications (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)

2.3. Known issues

This section provides highlighted known issues in Migration Toolkit for Applications (MTA) version 7.3.2.

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.

As a workaround, Maven search can be disabled: you can manually set --disable-maven-search=true for CLI analysis and set disable_maven_search: true in the Tackle custom resource of the MTA operator for an analysis in the user interface. (MTA-6045)

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:

error: 'unable to ask for Konveyor rule entry'
Copy to Clipboard Toggle word wrap

To work around this problem, assign Maven credentials to the application or set these credentials as default before running the application analysis.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat