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
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.
These release notes cover all z-stream releases of MTR 1.0 with the most recent release listed first.
Chapter 2. MTR 1.0.2
2.1. New features
This section describes the new features of the Migration Toolkit for Runtimes (MTR) 1.0.2.
New Rulesets
MTR includes new rulesets to support users migrating to EAP 8 and Hibernate 6.
2.2. Known issues
For a complete list of all known issues, see the list of MTR 1.0.2 known issues in Jira.
2.3. Resolved issues
For a complete list of all issues resolved in this release, see the list of MTR 1.0.2 resolved issues in Jira.
Chapter 3. MTR 1.0.1
3.1. New features
This section describes the new features of the Migration Toolkit for Runtimes (MTR) 1.0.1.
New ruleset for Jakarta Faces 4.0
MTR includes a new ruleset for Jakarta Faces 4.0 to improve support for migrating to JBoss EAP 8.
3.2. Known issues
For a complete list of all known issues, see the list of MTR 1.0.1 known issues in Jira.
3.3. Resolved issues
For a complete list of all issues resolved in this release, see the list of MTR 1.0.1 resolved issues in Jira.
Chapter 4. MTR 1.0.0
4.1. New features
This section describes the new features of the Migration Toolkit for Runtimes (MTR) 1.0.0 as compared to the Migration Toolkit for Applications (MTA) 5.3.
Additional Migration paths
New transformation targets are available in MTR 1.0.2:
- 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.xmlfiles - Replacing package import statements
- Updating XML deployment descriptors
- Updating configuration properties
- 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.
4.2. Known issues
For a complete list of all known issues, see the list of MTR 1.0.0 known issues in Jira.
4.3. Resolved issues
At the time of the release, the following resolved issues have been identified as major issues worth highlighting:
Table 4.1. Major resolved issues
| ID | Component | Summary |
|---|---|---|
| MTR CLI |
Tag-related CLI arguments, | |
| 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. | |
| None |
|
For a complete list of all issues resolved in this release, see the list of MTR 1.0.0 resolved issues in Jira.
