Known issues and limitations

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

Applications 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. You must 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.