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.2.1.
Rules for migrating from Java EE8 to Jakarta EE9 and OpenRewrite support are both provided as Technology Preview only. 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.
Rules for migrating from Java EE8 to Jakarta EE9
MTA rules replace Java EE8 artifact dependencies and package import statements and rename XML schema namespaces, prefixed properties, and bootstrapping files for Jakarta EE9. You run these rules by specifying the jakarta-ee
target.
OpenRewrite recipe support
OpenRewrite automates large-scale, distributed source code refactoring. You can run OpenRewrite recipes by using the MTA CLI.
The recipe org.jboss.windup.JavaxToJakarta
renames imported javax
packages to their jakarta
equivalents.
MTA extension for Visual Studio Code compatible with Codespaces
The MTA extension for Microsoft Visual Studio Code is now compatible with Microsoft Visual Studio Codespaces.
Rules for the Springboot-to-Quarkus migration path
Rulesets identify Quarkus-supported technologies by detecting a POM dependency, embedded JAR file, or a partial file path within an Apache Maven Shade uber JAR.
The rules identify the following technologies:
- Apicurio Studio
- Flyway
- Liquibase
- Liquibase for MongoDB
- OpenTelemetry
- Picocli
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.2.1 known issues in Jira.
Table 2.1. Major known issues
ID | Component | Summary |
---|---|---|
CodeReady Workspace plugin | The plugin works with CodeReady Workspace 2.09, but not version 2.10. | |
Web console on OpenShift Container Platform | Analysis fails when MTA custom labels are uploaded and advanced options are enabled. | |
Web console on OpenShift Container Platform | If you run an analysis on multiple applications and subsequently delete an application and rerun the analysis, the analysis hangs. | |
Web console | The Save and Save and run buttons are not displayed on the Custom rules and Custom labels tabs on the Analysis configuration page. | |
Web console | If you delete an application from a project after running an analysis, the number of applications is not updated when you rerun the analysis. |
Chapter 3. Resolved issues
At the time of the release, the following resolved issues have been identified as major issues worth highlighting:
Table 3.1. Major resolved issues
ID | Component | Summary |
---|---|---|
Red Hat CodeReady Studio extension | The plugin cannot be used in Red Hat CodeReady Studio 12.21.0.GA. | |
ItelliJ IDEA plugin and Visual Studio Code extension | The Apply QuickFix menu option is not disabled after a QuickFix is applied. | |
ItelliJ IDEA plugin | After you run an analysis, the Mark as Complete menu option is not displayed. | |
Visual Studio Code extension | If you run an analysis with an incorrect JAVA_HOME environmental variable, the analysis continues to run after you correct the variable and the Run option is disabled. |