Chapter 1. New features
This section describes the new features of the Migration Toolkit for Applications (MTA) 5.1.4.
Updated web console interface
The current release contains an updated web console interface with improved project management features and additional transformation targets.
Migration Toolkit for Applications Operator for OpenShift Container Platform
The current release contains the Migration Toolkit for Applications Community Operator for installing the web console on OpenShift Container Platform 4.6 and later versions.
Installation in multiple namespaces on OpenShift Container Platform
The current release can be installed in multiple namespaces on OpenShift Container Platform. Previously, the web console could be installed in only one namespace.
Additional rules for migrating from Spring Boot to Quarkus
The current release contains additional rules for migrating from Spring Boot to Quarkus. The target of these rules is
The new rules identify Spring Boot APIs that are implemented in Quarkus Spring extensions, where Spring Boot dependencies can be replaced by equivalent Quarkus extensions. The rules also report Spring artifacts that do not have Quarkus equivalents.
The rules identify application dependencies for which there are equivalent Quarkus extensions, including the following:
- Amazon DynamoDB
- Amazon IAM
- Amazon S3
- Amazon Simple Email Service
- Amazon Simple Notification Service
- Amazon Simple Queue Service
- AWS Config
- AWS Key Management Service
- AWS Lambda with HTTP APIs
- AWS Lambda with AWS X-Ray
- Apache Avro
- Apache Kafka
Java Database Connectivity rules for the following databases:
- Apache Derby
- OpenShift Container Platform
- WildFly Elytron
Rules for migrating to the latest version of Quarkus
The current release contains rules for migrating to the latest version of Quarkus. The target of these rules is
quarkus<version>, for example,
quarkus1:13 for Quarkus 1.13.x.
These rules ensure that the applications are migrated to a target that has the latest features, resolved issues, and patches.
These rules will be updated for future Quarkus releases.
Rules for migrating from Thorntail to JBoss EAP XP 2
The current release contains rules for migrating from Thorntail to JBoss EAP XP 2. The target of these rules is
For more information about this migration path, see the Red Hat JBoss EAP XP 2.0.0 Migration Guide.