Release Notes
New features, known issues, and resolved issues
Abstract
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. Introduction
These release notes describe the new features and changes implemented for the Migration Toolkit for Applications (MTA) 5.0 release.
Chapter 2. New features
This section describes the new features of the Migration Toolkit for Applications.
- Rebranding
- The Red Hat Application Migration Toolkit has been rebranded as the Migration Toolkit for Applications (MTA).
- New migration path for migrating to Apache Camel 3
- The current release contains a new migration path to support the migration from Apache Camel 2 to Apache Camel 3. The Camel 3 rulesets contain 147 new rules.
Chapter 3. Known issues
At the time of release, the following known issues are identified as major issues. For a full list of all known issues and issues that have been identified, see open MTA issues.
ID | Component | Summary |
---|---|---|
Eclipse Plugin | You cannot run the IDE plugin 5.0.1 with Eclipse 2020-06 because a null pointer exception causes analyses to fail. | |
Lifecycle (Runtime) | On RHEL CSB, MTA web console 5.0.0 fails after artifact upload. | |
Web UI & Windup-as-a-Service | MTA 5.0 does not support Internet Explorer. | |
Web UI & Windup-as-a-Service |
On macOS, the | |
Web UI & Windup-as-a-Service |
On macOS, the | |
OpenShift | RHAMT 4.3.1 installation on OpenShift Container Platform fails. The Webconsole and Executor Pods are not running. | |
Web UI & Windup-as-a-Service |
| |
Migration - Application |
| |
Technical Debt | RHAMT does not run on Zulu. | |
Web UI & Windup-as-a-Service | Global custom rules might appear in the Project level Select Custom Rules screen. | |
Web UI |
After running an analysis, clicking the Short Reports link results in a | |
Rule Execution - XML-based | Regex pattern-matching is not working properly. | |
Web UI |
After running an analysis, clicking the Results icon results in a | |
OpenShift Deployment | Cannot access reports when RHAMT 4.1.0 is installed on OpenShift Container Platform | |
Eclipse Plugin | Run configuration must be updated to include JDK instead of JRE. | |
Windup Maven Plugin |
Because of dependency issues, | |
IDE Plugin | Sometimes the Eclipse plugin cannot connect to the RHAMT server it spawned. | |
OpenShift Deployment | Liveness probe of the Message Executor Pod is tied to the web console. | |
IDE Plugin | Plugin updates require better support. | |
Web UI & Windup-as-a-Service | Incorrect time is displayed on the Analysis Results screen if there is a discrepancy between the server and client clocks. | |
Eclipse Plugin | Issue Explorer does not display analysis results after running an analysis. | |
Web UI & Windup-as-a-Service | In the Issues screen for applications, the Embedded framework and Embedded library fields do not show files. |
Chapter 4. Resolved issues
At the time of release, the following issues are resolved.
ID | Summary |
---|---|
Java | |
|