Chapter 3. MTA 7.2.0 3.1. New features This section provides the new features and improvements of the Migration Toolkit for Applications (MTA) 7.2.0. 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 . 3.2. Resolved issues This section provides highlighted issues that have been resolved in Migration Toolkit for Applications (MTA) 7.2.0. Tags are not accessible in SVN repositories In 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 versions of MTA, importing applications using a CSV after a 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 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 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 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 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) For a complete list of all resolved issues, see the list of MTA 7.2.0 resolved issues in Jira. 3.3. Known issues This section provides highlighted known issues in Migration Toolkit for Applications (MTA) version 7.2.0. 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) For a complete list of all known issues, see the list of MTA 7.2.0 known issues in Jira.

Commands: