MTA-2204-Changes-needed-for-mta-cli-docs#848
Conversation
Signed-off-by: Andy Arnold <anarnold@redhat.com>
✅ Deploy Preview for windup-documentation ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Andy Arnold <anarnold@redhat.com>
Signed-off-by: Andy Arnold <anarnold@redhat.com>
|
@anarnold97 Please check "Running MTA on source code" again -- the preview of the code block shows both --previews and eap:6 . Wonder if his comments apply to the rest of the section? The rest is LGTM. |
|
|
||
| [NOTE] | ||
| ==== | ||
| To run the {ProductShortName} command without prompting, for example when executing from a script, you must use the following arguments: |
There was a problem hiding this comment.
without prompting to be removed. The new mta-cli doesn't prompt anymore
|
|
||
| |--help |Display the {ProductShortName} help message. | ||
| |--input |A space-delimited list of the path to the file or directory containing one or more applications to be analyzed. This argument is required. | ||
| |--listTags| Flag to list all available tags. |
| |--input |A space-delimited list of the path to the file or directory containing one or more applications to be analyzed. This argument is required. | ||
| |--listTags| Flag to list all available tags. | ||
| |--list-targets| Flag to list all available target technologies. | ||
| |--mavenize| Flag to create a Maven project directory structure based on the structure and content of the application. This creates `pom.xml` files using the appropriate Java EE API and the correct dependencies between project modules. See also the `--mavenizeGroupId` option. |
| |--listTags| Flag to list all available tags. | ||
| |--list-targets| Flag to list all available target technologies. | ||
| |--mavenize| Flag to create a Maven project directory structure based on the structure and content of the application. This creates `pom.xml` files using the appropriate Java EE API and the correct dependencies between project modules. See also the `--mavenizeGroupId` option. | ||
| | -m, --mode string | Flag for analysis mode" `full` (default) or `source-only` |
| | --rules stringArray | Filename or directory containing rule files | ||
| |--source |A space-delimited list of one or more source technologies, servers, platforms, or frameworks to migrate from. This argument, in conjunction with the `--target` argument, helps to determine which rulesets are used. Use the `--listSourceTechnologies` argument to list all available sources. | ||
| |--target |A space-delimited list of one or more target technologies, servers, platforms, or frameworks to migrate to. This argument, in conjunction with the `--source` argument, helps to determine which rulesets are used. Use the `--listTargetTechnologies` argument to list all available targets. | ||
| |--userIgnorePath |Specify a location, in addition to `${user.home}/.{LC_PSN}/ignore/`, for {ProductShortName} to identify files that should be ignored. |
There was a problem hiding this comment.
Remove this line as the option no longer exists
| Do not overwrite a report output directory that contains important information. | ||
| ==== | ||
| | --rules stringArray | Filename or directory containing rule files | ||
| |--source |A space-delimited list of one or more source technologies, servers, platforms, or frameworks to migrate from. This argument, in conjunction with the `--target` argument, helps to determine which rulesets are used. Use the `--listSourceTechnologies` argument to list all available sources. |
There was a problem hiding this comment.
--listSourceTechnologies to be replaced with --list-sources
| ==== | ||
| | --rules stringArray | Filename or directory containing rule files | ||
| |--source |A space-delimited list of one or more source technologies, servers, platforms, or frameworks to migrate from. This argument, in conjunction with the `--target` argument, helps to determine which rulesets are used. Use the `--listSourceTechnologies` argument to list all available sources. | ||
| |--target |A space-delimited list of one or more target technologies, servers, platforms, or frameworks to migrate to. This argument, in conjunction with the `--source` argument, helps to determine which rulesets are used. Use the `--listTargetTechnologies` argument to list all available targets. |
There was a problem hiding this comment.
--listTargetTechnologies to be replaced with --list-targets
Jira
Preview