Red Hat SummitRelease 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.3.0.
Analyze Known Libraries
You can now use the analyzeKnownLibraries advanced option to analyze libraries embedded within your applications. This feature lets you go beyond the default behavior of MTA, which is to only analyze application code.
Rules for migrating from OpenJDK 8 to OpenJDK 11
MTA now includes rules to help you migrate applications from OpenJDK 8 (Java 8) to 11.
Technology Reports
The technology reports have been enriched. The reports include new technologies, technology tags, and technology classifications.
Apply all Quick Fixes
In the MTA IDE plugins and extensions, you can now apply all suggested quick fixes at once, rather than one by one.
Rules for migrating from Spring Boot to Quarkus
Additional rules have been added to support migrating from Spring Boot to Quarkus.
Rules for migrating from IBM WebSphere to Open Liberty
A comprehensive collection of rules has been added to support migrating traditional IBM WebSphere applications to Open Liberty.
New OpenRewrite capabilities including additional recipes
- The integration of MTA with OpenRewrite has been extended to support multiple migration paths.
-
An additional recipe for the
javaxtojakartatransformation path has been added, as well as the first Spring Boot to Quarkus recipe.
OpenRewrite 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.
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 MTA 5.3.0 known issues in Jira.
| ID | Component | Summary |
|---|---|---|
| Migration - Application |
The | |
| IntelliJ extension |
When you run an analysis via the extension, an exception related to | |
| Web console |
There is no option in the web console to navigate to or to download mavenized | |
| Web console on OpenShift Container Platform | When you upload MTA custom labels and enable advanced options, analysis fails. | |
| Web console | When you edit any project and make any changes to a custom rule or a custom label, the Save and Save and Run buttons remain disabled. Workaround: You can make these changes in the Analysis configuration screen. | |
| Web console | When an analysis that you run on OpenShift Container Platform from MTA fails, logs are not visible. | |
| OpenShift Container Platform | When you enable FIPS on OpenJDK 11 and then install MTA 5.3.0.Final on OpenShift Container Platform, some pods do not come up. |
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 MTA 5.3.0 resolved issues in Jira.
| ID | Component | Summary |
|---|---|---|
| Web console on OpenShift Container Platform | Custom rules do not work on OpenShift Container Platform. | |
| Rules engine | When an analysis using source mode is run on an application source directory that has the target subdirectory, the contents of the target subdirectory are added to the analysis scope. This leads to duplication or possible errors in the results. | |
| Migration - Application |
The | |
| Rules engine | POM files inside a binary are not consistently analyzed. | |
| Web console | There is a package discovery problem in the MTA web console when running in source mode. |
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}