Red Hat Application Migration Toolkit 4.2.1 Release Notes

Red Hat Application Migration Toolkit 4.2

New features and changes in this release.

Red Hat Customer Content Services

Abstract

These release notes describe the new features and changes implemented for the Red Hat Application Migration Toolkit (RHAMT) 4.2.1 release.

Chapter 1. Introduction

These release notes describe the new features and changes implemented for the Red Hat Application Migration Toolkit (RHAMT) 4.2.1 release.

The RHAMT 4.2.1 release is a point release that focuses primarily on addressing issues and improving usability.

Chapter 2. New Features

2.1. Java 11 Support

This release introduces support for Java 11 as Technology Preview. Users can now run this distribution of RHAMT and generate reports using this version of Java.

Important

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.

2.2. Red Hat JBoss Enterprise Application Platform 7.2 Migration Path

Rules for Red Hat JBoss Enterprise Application Platform (JBoss EAP) 7.2 have been included in this release. When specifying eap:7 as the target release the generated reports will now highlight issues pertaining to JBoss EAP 7.2 migration paths.

2.3. OpenShift Installation Update

This release introduces new templates and an installation procedure for RHAMT on OpenShift.

Details on these templates are found at Understanding the Web Console OpenShift Image and Deploy the RHAMT Application.

2.4. Inclusive CSV Report

When specifying the --exportCSV argument, an AllIssues.csv file is now generated in the root directory of the report.

This file includes all discovered issues, spanning all analyzed applications, in addition to the individual CSV files generated per application.

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 this JIRA filter.

Table 3.1. Known Issues

IDComponentSummary

WINDUP-2333

OpenShift

Cannot access reports when RHAMT installed on OCP

WINDUP-2325

Web Console

Unzip install fails due to existence of .failed files

WINDUP-2304

Eclipse Plugin

Update run configuration to include JDK instead of JRE

WINDUP-2297

Maven Plugin

Dependency conflicts on org.apache.maven:maven-model:jar, causing unexpected code behaviors

WINDUP-2264

Eclipse Plugin

Sometimes the eclipse plugin can’t connect to the rhamt server it just spawned

WINDUP-2147

OpenShift

liveness probe for executor pod is tied to web console

WINDUP-2122

Eclipse Plugin

Better support for cleanly updating from one version of the plugin to another.

WINDUP-2025

Web Console

Wrong time is displayed on analysis result page when there’s an offset between server and client time

WINDUP-2010

Eclipse Plugin

Issue Explorer not populating results after analysis

WINDUP-1972

Web Console

Issues in application view: Embedded Framework / library doesn’t show file

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 this JIRA filter.

Table 4.1. Resolved Issues

IDSummary

WINDUP-2277

RHAMT on Openshift - Package Discovery service causes the WebUi Pod to run out of memory

WINDUP-2238

Warnings are shown when launching web console

WINDUP-2177

Enrich mouse over information on tech punch card

WINDUP-1986

Maven plugin should come with a default value for windupVersion

WINDUPRULE-178

Non-JPA applications that use Hibernate with JTA must set hibernate.transaction.coordinator_class

Legal Notice

Copyright © 2019 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.