Known issues and limitations

Learn about known issues and limitations for Application Modernization Accelerator Developer Tools.

Applications that are built with non-Maven build tools

Some aspects of modernizing your application that you can do with a Maven-built application you cannot do for an application that is built with another build tool. The following limitations apply when you build your applications with non-Maven build tools.

No automated fixes are available.
Application Modernization Accelerator Developer Tools cannot build an application that is not built by using Maven. Build the application manually so that the application binary can be analyzed.
Application Modernization Accelerator Developer Tools cannot discover the location of the application binary, which it needs when it analyzes an application.
You need to specify the location.
The modernization process cannot set the recommended Java version in the Java version menu when it is doing analysis.
The recommended Java version is chosen based on the Java version in the build configuration. However, the version cannot be detected in non-Maven builds.
The application modernization process puts the server.xml file in the project root directory.
You can move it to a location where your WebSphere® Application Server Liberty installation expects it to be.

Supported migration plan versions

Using a migration plan from Application Modernization Accelerator version 5 or later with a version of Application Modernization Accelerator Developer Tools before version 2.0 is not supported.

Migration plans generated before Application Modernization Accelerator version 5 (including plans from Transformation Advisor) can be used with Application Modernization Accelerator Developer Tools 2.0 only if entitlement is established with access keys or migration plans from Application Modernization Accelerator Developer Tools 5.0 or later.

Group migration plans are not supported

Group migration plans from Application Modernization Accelerator are not supported in Application Modernization Accelerator Developer Tools. Group migration plans contain information for multiple applications.

The modernization flows in Application Modernization Accelerator Developer Tools can process only one application at a time. Export an individual migration plan from Application Modernization Accelerator for use with Application Modernization Accelerator Developer Tools. Application Modernization Accelerator Developer Tools considers a group migration plan to be invalid.

Supported Java version is set automatically

When the version of Java that is configured in the pom.xml file is not supported on the source application server, then Application Modernization Accelerator Developer Tools sets the closest supported Java version when it performs an analysis.

For example, if source runtime environment = WebSphere Application Server 8.0 and source Java SE = 8 are set in the pom.xml file, the analysis runs with the source Java version set to 6. This change occurs because Java 6 is supported on WebSphere Application Server 8, but Java 8 is not.

Java upgrade rule recipes might run unexpectedly

When the version of Java that is configured in the pom.xml file is not supported on the source application server, and you select to not change the Java version, Java rules are still run. For example, given the following settings:

source runtime environment = WebSphere Application Server 9.0
target runtime environment = Modernized Runtime Extension for Java (MoRE)
source Java SE = 17 (detected from pom.xml file)
target Java SE = 17

The scan runs with source Java SE = 8 and target Java SE = 17. This change occurs because the configured Java 17 is not supported on the selected source runtime environment, WebSphere Application Server 9.0. This configuration might cause undesired and confusing code changes from the general rule recipes for upgrading Java.

To avoid unexpected results, ensure that your selected source and target versions are correct. In the example, an application that is targeted for Java 17 would not actually run on WebSphere Application Server 9.0.

Detected source Java version

When you select the source Java SE version, Application Modernization Accelerator Developer Tools lists the Java SE versions that are valid for the source runtime environment. The level of Java from your current build configuration for a Maven application is labeled as the detected version. If you select an earlier version than the detected version, problems might occur when you build and run automations.

Earliest Java EE version that can be migrated

Java EE 6 is the earliest version for which a ruleset exists. Version 6 is the version that is used in cases where an earlier version is indicated. For example, WebSphere Application Server 6.1 with IBM Java 5 has no supported EE version, so EE 6 is used as the source EE version.

Display issue for the web view cursor in IntelliJ IDEA

You might experience cursor display issues such as the hand cursor not showing in the plug-in's web view components. If you do, you can configure the JCEF browser to run in local mode instead of remote mode. Complete the following steps to change the mode.

Click Help > Edit Custom VM Options....
Add the following line:
```
-Djcef.remote.enabled=false
```
Restart IntelliJ IDEA.

Finish a modernization before you upgrade Application Modernization Accelerator Developer Tools

Complete the modernization of an application on your current version of Application Modernization Accelerator Developer Tools before you upgrade it (or roll it back) to a different version.