-
Language:
English
-
Language:
English
Red Hat Application Migration Toolkit 4.3.0 Release Notes
New features and changes in this release.
Abstract
Chapter 1. Introduction
These release notes describe the new features and changes implemented for the Red Hat Application Migration Toolkit (RHAMT) 4.3.0 release.
Chapter 2. New Features
2.1. Target Runtime Labels (including custom Target Runtime Labels)
The Target Runtime feature assesses all of the Technology Tags identified for each application for compatibility with specific runtimes. JBoss EAP and JWS are the two Target Runtime definitions that are included in the RHAMT distribution. Target Runtime definitions are extensible enabling you to use custom Target Runtimes in analysis executions.
2.2. RHAMT extension for Visual Studio Code and Eclipse Che
This release introduces a Minimum Viable Product version of a RHAMT extension for Visual Studio Code and Eclipse Che. The extension contains all of the core features required to perform a RHAMT analysis in your development environment. For more information about the extension, visit the Visual Studio Markteplace. Note, that this release of the RHAMT extension for Visual Studio Code and Eclipse Che is a Minimum Viable Product release, and is still in development.
2.3. New Rules for migrating Spring Boot to Red Hat Runtimes
This release introduces a new set of rules for assessing the compatibility of applications against the versions of Spring Boot libraries supported by Red Hat Runtimes. These rules are executed when the rhr target is selected in the RHAMT analysis configuration.
2.4. New rule condition: <dependency>
A new rule feature that can check the Group, Artifact and Version on all dependencies of an application. This feature was used to develop the new Spring Boot ruleset.
2.5. Updated Web UI and Reports
The Web application has been updated to version 7 of Angular resulting in a much more intuitive and modern user interface. The presentation of the RHAMT reports has been improved by upgrading them to Bootstrap version 3.4.1.
2.6. Custom Rules with project and global scope
Custom Rules, and Custom Target Runtime Labels, can be configured to have a project scope or a global scope. This means that you can activate them on one project or on all of your projects.
Chapter 3. Known Issues
At the time of the release the following known issues have been identified as important issues worth highlighting. For a full list of all known issues and issues that have been identified since the release, see the 4.3.0 known issues JIRA filter.
Table 3.1. Known Issues
| ID | Component | Summary |
|---|---|---|
| Web console | RHAMT 4.2.1 web based throws forbidden issue | |
| IDE Plugin | After analysis, clicking on the short reports link results in a not found page | |
| Rule execution - XML-based | Pattern matching regular expressions does not work properly | |
| Maven Plugin |
RHAMT is showing HTTP Error | |
| OpenShift | Cannot access reports when RHAMT is installed on OCP | |
| IDE Plugin | Update run configuration to include JDK instead of JRE | |
| Maven Plugin |
Dependency conflicts on | |
| IDE Plugin | The IDE plugin sometimes cannot connect to the RHAMT server it just spawned | |
| OpenShift | The liveness probe for the message executor pod is tied to Web console | |
| IDE Plugin | Better support for cleanly updating from one version of the plugin to another | |
| Web console | Incorrect time is displayed on analysis result page when there is an offset between server and client time. | |
| IDE Plugin | Issue Explorer not populating results after analysis | |
| Web Console | Issues in application view: Embedded Framework / library doesn’t show file | |
| Reporting | RHAMT Reports - Hard Coded IP Address link to Source Report does not have the correct line in focus | |
| Web Console | RHAMT Web UI - Configuration - Warning about losing changes is displayed when no changes were made to the configuration. | |
| Web Console | RHAMT Web UI - Configuration - Warning about losing changes is displayed when no changes were made to the configuration. |
Chapter 4. Resolved Issues
At the time of the release the following resolved issues have been identified as important issues worth highlighting. For a full list of all issues resolved in this release, see the 4.3.0 known issues JIRA filter.
Table 4.1. Resolved Issues
| ID | Summary |
|---|---|
| RHAMT on OpenShift: Change suggested RHAMT Web UI URL | |
| RHAMT on OpenShift: Application List Filtering/Labelling to support Target Runtime Selection | |
| RHAMT on OpenShift: Application List Report - Technology Tags | |
| RHAMT on OpenShift: Wrong label in "Included Package" when empty | |
| Web console User Experience: app upload: Change upload failure errors | |
| Web console User Experience: Export all-in-one CSV file from Web console | |
| RHAMT Web Console: Package Selection: Application Packages not checked for selection by default | |
| RHAMT Web Console: Upgrade Angular | |
|
RHAMT Web Console: |
