Release Notes

Table of Contents

• Making open source more inclusive
• 1. Introduction
• 2. New features
• 3. Known issues
• 4. Resolved issues

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. Introduction

Migration Toolkit for Runtimes (MTR) provides an extensible and customizable rule-based tool that simplifies the migration and modernization of Java applications, such as migrating JBoss Enterprise Application Platform (EAP) 7 to 8 or migrating from any other application server towards EAP at scale. MTR provides the same migration solution as provided in the Migration Toolkit for Applications 5 releases.

2. New features

This section describes the new features of the Migration Toolkit for Runtimes (MTR) 1.0 as compared to Migration Toolkit for Applications (MTA) 5.3.

Additional Migration paths

New transformation targets are available in MTR 1.0.0:

• OpenJDK 11 to OpenJDK 17

• EAP and Spring Boot applications to Azure App Service

• Java EE 8 to Jakarta EE 9

• EAP 7 to EAP 8 (Beta)

Openrewrite recipes to automate the Java EE 8 to Jakarta EE 9 transformations

The Openrewrite recipes automate the following:

• Replacing dependencies declared in pom.xml files

• Replacing package import statements

• Updating XML deployment descriptors

• Updating configuration properies

• Renaming SPI files

Improved pom.xml analysis

MTR can search for artifacts within the parent, dependencyManagement, dependencies, pluginManagement and plugin blocks.

YAML file source code report

The Source Code Report is compatible with YAML files, so migration issues can be highlighted in the context of the YAML file in which they were discovered.

Transaction Report (Tech Preview)

A new transaction report is now available in the application analysis reports. This new option analyzes the application data layer and provides detailed information about how transactions propagate across different layers. The report presents the information as a sequence of service entries, call graphs and SQL statements.

3. Known issues

For a complete list of all known issues, see the list of MTR 1.0 known issues in Jira.

4. Resolved issues

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

Table 1. Major resolved issues

ID	Component	Summary
WINDUP-3227	MTR CLI	Tag-related CLI arguments, --includeTags and --excludeTags, do not work properly.
WINDUP-3482	MTR web console	The web console is unable to discover packages present in the application and does not allow the user to create a project.
WINDUP-3312	None	DiscoverHardcodedIPAddressRuleProvider.java does not detect hardcoded IP addresses in Java classes.

For a complete list of all issues resolved in this release, see the list of MTR 1.0.0 resolved issues in Jira.