Skip to content

Latest commit

 

History

History
55 lines (38 loc) · 3.11 KB

assembly_analyzing-applications-mta-cli.adoc

File metadata and controls

55 lines (38 loc) · 3.11 KB

Analyzing Java applications with {ProductShortName} command-line interface

Assess and prioritize migration effort by analyzing your Java applications with the {ProductFullName} CLI. Run single- or multiple-app analysis and get reports that highlight required changes.

Depending on your scenario, you can use the {ProductShortName} CLI to perform the following actions:

  • Run the analysis against a single application.

  • Run the analysis against multiple applications:

    • In {ProductShortName} versions earlier than 7.1.0, you can enter a series of --analyze commands, each against an application and each generating a separate report. For more information, see Running the {ProductShortName} {CLINameTitle} against an application.

    • In {ProductShortName} version 7.1.0 and later, you can use the --bulk option to analyze multiple applications at once and generate a single report. Note that this feature is a Developer Preview feature only. For more information, see Analyzing multiple applications.

Important

Starting from {ProductShortName} version 7.2.0, you can run the application analysis for Java applications in the containerless mode. Note that this option is set by default and is used automatically only if all requirements are met. For more information, see Analyzing an application in the containerless mode.

However, if you want to analyze applications in languages other than Java or, for example, use transformation commands, you still need to use containers.
Note

The analysis output in the disconnected environment usually results in fewer incidents because a dependency analysis does not run accurately without access to Maven.

{ProductShortName} CLI supports running source code and binary analysis by using analyzer-lsp. analyzer-lsp is a tool that evaluates rules by using language providers.