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. New features
This section describes the new features of the Migration Toolkit for Applications (MTA) 5.1.4.
Updated web console interface
The current release contains an updated web console interface with improved project management features and additional transformation targets.
Migration Toolkit for Applications Operator for OpenShift Container Platform
The current release contains the Migration Toolkit for Applications Community Operator for installing the web console on OpenShift Container Platform 4.6 and later versions.
Installation in multiple namespaces on OpenShift Container Platform
The current release can be installed in multiple namespaces on OpenShift Container Platform. Previously, the web console could be installed in only one namespace.
Additional rules for migrating from Spring Boot to Quarkus
The current release contains additional rules for migrating from Spring Boot to Quarkus. The target of these rules is quarkus.
The new rules identify Spring Boot APIs that are implemented in Quarkus Spring extensions, where Spring Boot dependencies can be replaced by equivalent Quarkus extensions. The rules also report Spring artifacts that do not have Quarkus equivalents.
The rules identify application dependencies for which there are equivalent Quarkus extensions, including the following:
- Agroal
- Amazon DynamoDB
- Amazon IAM
- Amazon S3
- Amazon Simple Email Service
- Amazon Simple Notification Service
- Amazon Simple Queue Service
- AWS Config
- AWS Key Management Service
- AWS Lambda with HTTP APIs
- AWS Lambda with AWS X-Ray
- Apache Avro
- Apache Kafka
- Artemis
- Hibernate
Java Database Connectivity rules for the following databases:
- Apache Derby
- DB2
- MariaDB
- MySQL
- PostgreSQL
- JSONB
- JSONP
- Keycloak
- Kubernetes
- Narayana
- OpenShift Container Platform
- RESTeasy
- WildFly Elytron
Rules for migrating to the latest version of Quarkus
The current release contains rules for migrating to the latest version of Quarkus. The target of these rules is quarkus<version>, for example, quarkus1:13 for Quarkus 1.13.x.
These rules ensure that the applications are migrated to a target that has the latest features, resolved issues, and patches.
These rules will be updated for future Quarkus releases.
Rules for migrating from Thorntail to JBoss EAP XP 2
The current release contains rules for migrating from Thorntail to JBoss EAP XP 2. The target of these rules is eapxp:2.
For more information about this migration path, see the Red Hat JBoss EAP XP 2.0.0 Migration Guide.
Chapter 2. Known issues
At the time of release, the following known issues have been identified as major issues worth highlighting.
For a complete list of all known issues, see the list of 5.1.4 known issues in Jira.
Table 2.1. Major known issues
| ID | Component | Summary |
|---|---|---|
| VS Code Extension | Quick Fix does not fix XML rules. | |
| VS Code Extension | Right-clicking a VS Code configuration and selecting Open does not always open the configuration. | |
| VS Code Extension | Quick Fix does not fix multiple rules. | |
| Eclipse Plugin | Installing the Eclipse plugin 5.0.0 on CodeReady Studio 12.16 requires Maven. | |
| Web UI & Windup-as-a-Service |
When RHAMT 4.3.1 is deployed on OpenShift Container Platform with the | |
| Eclipse Che Plugin | Quick Fix does not fix multiple rules. | |
| VS Code Extension |
| |
| Eclipse Che Plugin | MTA Explorer commands do not work in the Eclipse Che environment. | |
| Web UI & Windup-as-a-Service | When RHAMT 4.3.1 is deployed on OpenShift Container Platform, custom rules cannot be uploaded. | |
| Technical Debt | RHAMT does not run on Zulu. | |
| Web UI & Windup-as-a-Service | When RHAMT 4.2.1 is deployed on OpenShift Container Platform, long names of HTML files for reports are truncated. |
Chapter 3. Resolved issues
At the time of the release the following resolved issues have been identified as major issues worth highlighting.
For a complete list of all issues resolved in this release, see the list of 5.1.4 resolved issues in Jira.
Table 3.1. Major resolved issues
| ID | Summary |
|---|---|
| MTA reports load slowly, do not include Target Runtime labels on the Application List screen, and do not have working feedback controls. | |
| The web console installed on OpenShift 4.4 and earlier versions cannot access the generated reports over an HTTPS connection. | |
| The web console installed on OpenShift 4.5 and later versions cannot access the generated reports over an HTTPS connection. | |
|
Analysis of applications built with JDK 11 generates | |
| Lucene index builder mistakenly identifies Spring packages as application packages. | |
| CSV report cannot be exported if the Skip reports option is enabled. | |
| IDE plugin 5.0.1 cannot run with Eclipse 2020-06 because a null pointer exception causes analyses to fail. | |
| VS Code does not recognize custom CLI path in MTA settings. |
