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.

1. New features

This section describes the new features of the Migration Toolkit for Applications ({ProductShortName}) 5.2.1.

Rules for migrating from Java EE8 to Jakarta EE9

{ProductShortName} rules replace Java EE8 artifact dependencies and package import statements and rename XML schema namespaces, prefixed properties, and bootstrapping files for Jakarta EE9.

Most rules contain quick fixes to automate source code changes when using an {ProductShortName} IDE plugin or extension for Eclipse, Eclipse Che, IntelliJ IDEA, Microsoft Visual Studio Code, or Red Hat CodeReady Studio.

To execute the rules, use the target jakarta-ee.

OpenRewrite recipe support

OpenRewrite automates large-scale, distributed source code refactoring. You can execute OpenRewrite recipes by using the {ProductShortName} CLI.

The first OpenRewrite recipe, which is shipped with {ProductShortName} 5.2.1, renames imported javax packages to their jakarta equivalents.

Important

OpenRewrite recipe support is 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.
{ProductShortName} extension for Visual Studio Code compatible with Codespaces

The {ProductShortName} 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

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 1. Major known issues
ID Component Summary

WINDUP-3138

CodeReady Workspace plugin

The plugin works with CodeReady Workspace 2.09, but not version 2.10.

WINDUP-3165

Web console on OpenShift Container Platform

Analysis fails when {ProductShortName} custom labels are uploaded and advanced options are enabled.

WINDUP-3160

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.

WINDUP-3005

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.

3. Resolved issues

At the time of the release, the following resolved issues have been identified as major issues worth highlighting:

Table 2. Major resolved issues
ID Component Summary

WINDUP-3125

ItelliJ IDEA plugin and Visual Studio Code extension

The Apply QuickFix menu option is not disabled after a QuickFix is applied.

WINDUP-3134

ItelliJ IDEA plugin

After you run an analysis, the Mark as Complete menu option is not displayed.

WINDUP-3136

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.