How to use Red Hat Migration Toolkit (MTA 7+) for Applications for Auto-Migration of an Application to the Jakarta EE 10 Namespace

Environment

• Migration Toolkit for Applications 7+
  • MTA cli

Issue

• How to migrate an application from Java EE to Jakarta EE 10?
• Migrate application to Jakarta EE 10?

Resolution

• For MTA CLI 7+, Run mta-cli command to migrate the javax to jakarta:

mta-cli analyze --input < war name> --output ./report-output-war/ --source eap7 --target eap8 --overwrite

• For MTA Operator select the EAP 8 target, similar to above.

Root Cause

MTA 7 does not have a specific Maven plugin and it is not based on Windup.
The article This content is not included.How to use Red Hat Migration Toolkit for Auto-Migration of an Application to the Jakarta EE 10 Namespace describes this for Windup/MTA 6, but it was retired because the fact the MTA 6 is End of Life.

Notes about EAP 7.4 Using Maven Repo.

Related Articles

• Red Hat JBoss EAP Application Migration from Jakarta EE 8 to EE 10
• Migrating a JBoss EAP Application's Maven Project (EAP BOMs) to EAP 8
• Content from windup.github.io is not included.Auto-migration of apps from Java EE 8 to Jakarta EE 9 using Windup and Openrewrite

Diagnostic Steps

Standard due diligence should be done in case of not returning results:
MTA-Cli:

• analysis log file
• details on Maven and Java collections

MTA Operator:

• Collect the Inspect
• Collect the Tackle Custom Resource
• Collect the analysis yaml with the merged view

In both cases: report (in case it was generated).

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.