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.