-
Language:
English
-
Language:
English
Red Hat Application Migration Toolkit 4.2.1 Release Notes
New features and changes in this release.
Abstract
Chapter 1. Introduction
These release notes describe the new features and changes implemented for the Red Hat Application Migration Toolkit (RHAMT) 4.2.1 release.
The RHAMT 4.2.1 release is a point release that focuses primarily on addressing issues and improving usability.
Chapter 2. New Features
2.1. Java 11 Support
This release introduces support for Java 11 as Technology Preview. Users can now run this distribution of RHAMT and generate reports using this version of Java.
Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
See Technology Preview Features Support Scope on the Red Hat Customer Portal for information about the support scope for Technology Preview features.
2.2. Red Hat JBoss Enterprise Application Platform 7.2 Migration Path
Rules for Red Hat JBoss Enterprise Application Platform (JBoss EAP) 7.2 have been included in this release. When specifying eap:7
as the target release the generated reports will now highlight issues pertaining to JBoss EAP 7.2 migration paths.
2.3. OpenShift Installation Update
This release introduces new templates and an installation procedure for RHAMT on OpenShift.
Details on these templates are found at Understanding the Web Console OpenShift Image and Deploy the RHAMT Application.
2.4. Inclusive CSV Report
When specifying the --exportCSV
argument, an AllIssues.csv
file is now generated in the root directory of the report.
This file includes all discovered issues, spanning all analyzed applications, in addition to the individual CSV files generated per application.
Chapter 3. Known Issues
At the time of the release the following known issues have been identified as important issues worth highlighting. For a full list of all known issues and issues that have been identified since the release, see this JIRA filter.
Table 3.1. Known Issues
ID | Component | Summary |
---|---|---|
OpenShift | Cannot access reports when RHAMT installed on OCP | |
Web Console | Unzip install fails due to existence of .failed files | |
Eclipse Plugin | Update run configuration to include JDK instead of JRE | |
Maven Plugin | Dependency conflicts on org.apache.maven:maven-model:jar, causing unexpected code behaviors | |
Eclipse Plugin | Sometimes the eclipse plugin can’t connect to the rhamt server it just spawned | |
OpenShift | liveness probe for executor pod is tied to web console | |
Eclipse Plugin | Better support for cleanly updating from one version of the plugin to another. | |
Web Console | Wrong time is displayed on analysis result page when there’s an offset between server and client time | |
Eclipse Plugin | Issue Explorer not populating results after analysis | |
Web Console | Issues in application view: Embedded Framework / library doesn’t show file |
Chapter 4. Resolved Issues
At the time of the release the following resolved issues have been identified as important issues worth highlighting. For a full list of all issues resolved in this release, see this JIRA filter.
Table 4.1. Resolved Issues
ID | Summary |
---|---|
RHAMT on Openshift - Package Discovery service causes the WebUi Pod to run out of memory | |
Warnings are shown when launching web console | |
Enrich mouse over information on tech punch card | |
Maven plugin should come with a default value for windupVersion | |
Non-JPA applications that use Hibernate with JTA must set hibernate.transaction.coordinator_class |