From aec3e82419ca1f83a6496b36ddec5aaa04b88452 Mon Sep 17 00:00:00 2001 From: emarcusRH Date: Sun, 4 Feb 2024 20:08:05 +0200 Subject: [PATCH 1/6] insert mta-cli attribute instead of plain text windup-cli --- docs/topics/cli-run.adoc | 24 +++++++++---------- docs/topics/create-first-xml-rule.adoc | 2 +- ...ntellij-idea-plugin-run-configuration.adoc | 2 +- docs/topics/manually-test-rules.adoc | 2 +- docs/topics/mavenize.adoc | 2 +- docs/topics/review-reports.adoc | 2 +- .../topics/templates/document-attributes.adoc | 2 ++ docs/topics/using-openrewrite-recipes.adoc | 10 ++++---- .../vs-code-extension-run-configuration.adoc | 4 ++-- 9 files changed, 26 insertions(+), 24 deletions(-) diff --git a/docs/topics/cli-run.adoc b/docs/topics/cli-run.adoc index 058ddf2b3f..87f7f6588a 100644 --- a/docs/topics/cli-run.adoc +++ b/docs/topics/cli-run.adoc @@ -11,11 +11,11 @@ You can run {ProductShortName} against your application. .Procedure . Open a terminal and navigate to the `<{ProductShortName}_HOME>/bin/` directory. -. Execute the `windup-cli` script, or `windup-cli.bat` for Windows, and specify the appropriate arguments: +. Execute the `{mta-cli}` script, or `{mta-cli}.bat` for Windows, and specify the appropriate arguments: + [source,terminal,subs="attributes+"] ---- -$ ./windup-cli --input /path/to/jee-example-app-1.0.0.ear \ +$ ./{mta-cli} --input /path/to/jee-example-app-1.0.0.ear \ --output /path/to/output --source weblogic --target eap:6 \ --packages com.acme org.apache ---- @@ -38,7 +38,7 @@ The following command analyzes the `com.acme` and `org.apache` packages of the l [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli \ +$ <{ProductShortName}_HOME>/bin/{mta-cli} \ --input /path/to/jee-example-app-1.0.0.ear \ --output /path/to/report-output/ --source eap:5 --target eap:7 \ --packages com.acme org.apache @@ -52,7 +52,7 @@ The following command analyzes the `org.jboss.seam` packages of the link:https:/ [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli --sourceMode --input /path/to/seam-booking-5.2/ \ +$ <{ProductShortName}_HOME>/bin/{mta-cli} --sourceMode --input /path/to/seam-booking-5.2/ \ --output /path/to/report-output/ --target eap:6 --packages org.jboss.seam ---- [] @@ -63,7 +63,7 @@ The following command analyzes the `com.acme` and `org.apache` packages of the l [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli --input /path/to/jee-example-app-1.0.0.ear \ +$ <{ProductShortName}_HOME>/bin/{mta-cli} --input /path/to/jee-example-app-1.0.0.ear \ --output /path/to/report-output/ \ --target eap:7 --target cloud-readiness --packages com.acme org.apache ---- @@ -76,7 +76,7 @@ To override the default _Fernflower_ decompiler, pass the `-Dwindup.decompiler` [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli -Dwindup.decompiler=procyon \ +$ <{ProductShortName}_HOME>/bin/{mta-cli} -Dwindup.decompiler=procyon \ --input --output \ --target --packages ---- @@ -88,7 +88,7 @@ The {ProductShortName} {CLIName} provides an option to enable Bash completion fo [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli [TAB] +$ <{ProductShortName}_HOME>/bin/{mta-cli} [TAB] ---- [discrete] @@ -99,7 +99,7 @@ To enable Bash completion for the current shell, execute the following command: [source,terminal,subs="attributes+"] ---- -$ source <{ProductShortName}_HOME>/bash-completion/windup-cli +$ source <{ProductShortName}_HOME>/bash-completion/{mta-cli} ---- [discrete] @@ -112,22 +112,22 @@ The following commands allow Bash completion to persist across restarts: + [source,terminal,subs="attributes+"] ---- -source <{ProductShortName}_HOME>/bash-completion/windup-cli +source <{ProductShortName}_HOME>/bash-completion/{mta-cli} ---- * To enable Bash completion for all users across system restarts, copy the {ProductName} {CLIName} Bash completion file to the `/etc/bash_completion.d/` directory as the root user. + [source,terminal,subs="attributes+"] ---- -# cp <{ProductShortName}_HOME>/bash-completion/windup-cli /etc/bash_completion.d/ +# cp <{ProductShortName}_HOME>/bash-completion/{mta-cli} /etc/bash_completion.d/ ---- [id="accessing-help_{context}"] == Accessing {ProductShortName} help -To see the complete list of available arguments for the `windup-cli` command, open a terminal, navigate to the `<{ProductShortName}_HOME>` directory, and execute the following command: +To see the complete list of available arguments for the `{mta-cli}` command, open a terminal, navigate to the `<{ProductShortName}_HOME>` directory, and execute the following command: [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli --help +$ <{ProductShortName}_HOME>/bin/{mta-cli} --help ---- diff --git a/docs/topics/create-first-xml-rule.adoc b/docs/topics/create-first-xml-rule.adoc index ebad527be8..b66f0dbdee 100644 --- a/docs/topics/create-first-xml-rule.adoc +++ b/docs/topics/create-first-xml-rule.adoc @@ -213,7 +213,7 @@ Open a terminal and run the following command, passing the test file as an input [options="nowrap",subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli --sourceMode --input /home//migration-rules/data --output /home//migration-rules/reports --target eap:6 +$ <{ProductShortName}_HOME>/bin/{mta-cli} --sourceMode --input /home//migration-rules/data --output /home//migration-rules/reports --target eap:6 ---- You should see the following result. diff --git a/docs/topics/intellij-idea-plugin-run-configuration.adoc b/docs/topics/intellij-idea-plugin-run-configuration.adoc index d55317f083..d8da21b5b6 100644 --- a/docs/topics/intellij-idea-plugin-run-configuration.adoc +++ b/docs/topics/intellij-idea-plugin-run-configuration.adoc @@ -20,7 +20,7 @@ The run configuration panel is displayed on the right. . Complete the following configuration fields: -** *cli*: Enter the path to the cli executable. For example: `$HOME/{LC_PSN}-cli-{ProductDistributionVersion}/bin/windup-cli`. +** *cli*: Enter the path to the cli executable. For example: `$HOME/{LC_PSN}-cli-{ProductDistributionVersion}/bin/{mta-cli}`. ** *Input*: Click *Add* and enter the input file or directory. ** *Target*: Select one or more target migration paths. + diff --git a/docs/topics/manually-test-rules.adoc b/docs/topics/manually-test-rules.adoc index 64a13377e1..b9e53d18bc 100644 --- a/docs/topics/manually-test-rules.adoc +++ b/docs/topics/manually-test-rules.adoc @@ -10,7 +10,7 @@ You can run an XML rule against your application file to test it: [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli [--sourceMode] --input --output --target --packages +$ <{ProductShortName}_HOME>/bin/{mta-cli} [--sourceMode] --input --output --target --packages ---- You should see the following result: diff --git a/docs/topics/mavenize.adoc b/docs/topics/mavenize.adoc index d5d3d63e04..be48c30d14 100644 --- a/docs/topics/mavenize.adoc +++ b/docs/topics/mavenize.adoc @@ -18,7 +18,7 @@ The following example runs {ProductShortName} using the link:https://github.com/ [source,options="nowrap",subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli --input /path/to/jee-example-app-1.0.0.ear --output /path/to/output --target eap:6 --packages com.acme org.apache --mavenize +$ <{ProductShortName}_HOME>/bin/{mta-cli} --input /path/to/jee-example-app-1.0.0.ear --output /path/to/output --target eap:6 --packages com.acme org.apache --mavenize ---- This generates the Maven project structure in the `/path/to/output/mavenized` directory. diff --git a/docs/topics/review-reports.adoc b/docs/topics/review-reports.adoc index 7252d0efe1..af34c232bd 100644 --- a/docs/topics/review-reports.adoc +++ b/docs/topics/review-reports.adoc @@ -13,7 +13,7 @@ The report was generated using the following command. [options="nowrap",subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/windup-cli --input /home/username/windup-cli-source/test-files/jee-example-app-1.0.0.ear/ --output /home/username/windup-cli-reports/jee-example-app-1.0.0.ear-report --target eap:6 --packages com.acme org.apache +$ <{ProductShortName}_HOME>/bin/{mta-cli} --input /home/username/{mta-cli}-source/test-files/jee-example-app-1.0.0.ear/ --output /home/username/{mta-cli}-reports/jee-example-app-1.0.0.ear-report --target eap:6 --packages com.acme org.apache ---- endif::cli-guide[] diff --git a/docs/topics/templates/document-attributes.adoc b/docs/topics/templates/document-attributes.adoc index 92a55e7d09..da21baa606 100644 --- a/docs/topics/templates/document-attributes.adoc +++ b/docs/topics/templates/document-attributes.adoc @@ -17,6 +17,7 @@ ifdef::mta[] :ProductShortName: MTA :ProductFullName: Migration Toolkit for Applications (MTA) :LC_PSN: mta +:mta-cli: mta-cli :DocInfoProductNameURL: migration_toolkit_for_applications :WebName: user interface :WebNameTitle: User Interface @@ -40,6 +41,7 @@ ifdef::mtr[] :ProductShortName: MTR :ProductFullName: Migration Toolkit for Runtimes (MTR) :LC_PSN: mtr +:mta-cli: windup-cli :DocInfoProductNameURL: migration_toolkit_for_runtimes :WebName: web console :WebNameTitle: Web Console diff --git a/docs/topics/using-openrewrite-recipes.adoc b/docs/topics/using-openrewrite-recipes.adoc index c6ae191457..7e15c2e6e6 100644 --- a/docs/topics/using-openrewrite-recipes.adoc +++ b/docs/topics/using-openrewrite-recipes.adoc @@ -18,11 +18,11 @@ For example, the OpenRewrite recipe `org.jboss.windup.JavaxToJakarta` renames im .Procedure -. Run `windup-cli`, specifying the recipe name, the path to the configuration file, and the application: +. Run `{mta-cli}`, specifying the recipe name, the path to the configuration file, and the application: + [source,terminal,subs="attributes+"] ---- -$ ./windup-cli --openrewrite --input \ +$ ./{mta-cli} --openrewrite --input \ "-Drewrite.configLocation=" \ "-DactiveRecipes=" --goal dryRun ---- @@ -49,11 +49,11 @@ You can include more than one recipe by specifying each in the `activeRecipes` p ** `dryRun` : The script returns a list of proposed changes. Ignore the `"Run 'mvn rewrite:run' to apply the recipes"` message. ** `run`: The script applies the changes. -. Run `windup-cli` with `--goal run` to apply the recipe: +. Run `{mta-cli}` with `--goal run` to apply the recipe: + [source,terminal,subs="attributes+"] ---- -$ ./windup-cli --openrewrite --input \ +$ ./{mta-cli} --openrewrite --input \ "-Drewrite.configLocation=" \ "-DactiveRecipes=" --goal run ----- \ No newline at end of file +---- diff --git a/docs/topics/vs-code-extension-run-configuration.adoc b/docs/topics/vs-code-extension-run-configuration.adoc index 699367d22b..009a1a1187 100644 --- a/docs/topics/vs-code-extension-run-configuration.adoc +++ b/docs/topics/vs-code-extension-run-configuration.adoc @@ -10,7 +10,7 @@ You can configure multiple run configurations to run against each project you im .Prerequisites -* `windup-cli` executable installed. You can download the `windup-cli` executable from link:{DevDownloadPageURL}[{LC_PSN} download]. +* `{mta-cli}` executable installed. You can download the `{mta-cli}` executable from link:{DevDownloadPageURL}[{LC_PSN} download]. .Procedure @@ -19,7 +19,7 @@ You can configure multiple run configurations to run against each project you im . Complete the following configuration fields: ** *Name*: Enter a meaningful name for the analysis configuration or accept the default. -** *cli*: Enter the path to the cli executable. For example: `$HOME/{LC_PSN}-cli-{ProductDistributionVersion}/bin/windup-cli`. +** *cli*: Enter the path to the cli executable. For example: `$HOME/{LC_PSN}-cli-{ProductDistributionVersion}/bin/{mta-cli}`. ** *Input*: Set to the path of the project that you have open within your IDE by clicking *Add* and doing one of the following: *** Enter the input file or directory and press Enter. From 8814ee2c35c741c7b513669b15f6683cd8d241ed Mon Sep 17 00:00:00 2001 From: Eli Marcus Date: Mon, 5 Feb 2024 18:33:32 +0200 Subject: [PATCH 2/6] Delete docs/topics/create-first-xml-rule.adoc seems to be causing a merge conflict --- docs/topics/create-first-xml-rule.adoc | 252 ------------------------- 1 file changed, 252 deletions(-) delete mode 100644 docs/topics/create-first-xml-rule.adoc diff --git a/docs/topics/create-first-xml-rule.adoc b/docs/topics/create-first-xml-rule.adoc deleted file mode 100644 index b66f0dbdee..0000000000 --- a/docs/topics/create-first-xml-rule.adoc +++ /dev/null @@ -1,252 +0,0 @@ -// Module included in the following assemblies: -// -// * docs/rules-development-guide/master.adoc - -:_content-type: PROCEDURE -[id="create-first-xml-rule_{context}"] -= Creating your first XML rule - -This section guides you through the process of creating and testing your first {ProductShortName} XML-based rule. This assumes that you have already installed {ProductShortName}. See link:{ProductDocUserGuideURL}/index#installing_and_running_the_cli[Installing and running the CLI] in the _{UserCLIBookName}_ for installation instructions. - -In this example, you will write a rule to discover instances where an application defines a `jboss-web.xml` file containing a `` element and provide a link to the documentation that describes how to migrate the code. - -[id="creating-directory-structure-for-the-rule_{context}"] -== Creating the directory structure for the rule - -Create a directory structure to contain your first rule and the data file to use for testing. - -[options="nowrap",subs="attributes+"] ----- -$ mkdir -p /home//migration-rules/rules -$ mkdir -p /home//migration-rules/data ----- - -This directory structure will also be used to hold the generated {ProductShortName} reports. - -[id="mta-creating-data-to-test-the-rule_{context}"] -== Creating data to test the rule - -. Create a `jboss-web.xml` file in the `/home//migration-rules/data/` subdirectory. -. Copy in the following content. -+ -[source,xml,subs="attributes+"] ----- - - - - - seam.jboss.org:loader=@projectName@ - java2ParentDelegation=false - - - ----- - -[id="creating-the-rule_{context}"] -== Creating the rule - -{ProductShortName} XML-based rules use the following rule pattern: - ----- -when(condition) - perform(action) -otherwise(action) ----- - -.Procedure - -. In the `/home//migration-rules/rules/` directory, create a file named `JBoss5-web-class-loading.windup.xml` that contains the following content: -+ -[source,xml,subs="attributes+"] ----- - - - - - - - - - - - - Reviewed-2015-05-01 - - - - - - - - - - - - ----- -+ -[NOTE] -==== -The XML file name must include the `.windup.xml` extension. Otherwise, {ProductShortName} does not evaluate the new rule. -==== - -. Add a unique identifier for the ruleset and rule: - -* Replace `` with an appropriate ruleset ID, for example, `JBoss5-web-class-loading`. -* Replace `` with an appropriate rule ID, for example, `JBoss5-web-class-loading_001`. - -. Add the following ruleset add-on dependencies: -+ -[source,xml,subs="attributes+"] ----- - - - - ----- - -. Add the source and target technologies: - -* Replace `` with `eap`. -* Replace `` with `eap`. - -. Set the source and target technology versions. -+ -* Replace `` with `(4,5)`. -* Replace `` with `(6,)`. - -+ -See the Apache Maven link:http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html[version range specification] for more information. - -. Complete the `when` condition. Because this rule tests for a match in an XML file, `xmlfile` is used to evaluate the files. -+ -To match on the `class-loading` element that is a child of `jboss-web`, use the xpath expression `jboss-web/class-loading`. -+ -[source,xml,subs="attributes+"] ----- - - - ----- -. Complete the `perform` action for this rule. -+ -* Add a classification with a descriptive title and a level of effort of `1`. -* Provide a hint with an informative message and a link to documentation that describes the migration details. -+ -[source,xml,subs="attributes+"] ----- - - - - - - The class-loading element is no longer valid in the jboss-web.xml file. - - - - - ----- - -The rule is now complete and should look like the following example. - -[source,xml,subs="attributes+"] ----- - - - - - This ruleset looks for the class-loading element in a jboss-web.xml file, which is no longer valid in JBoss EAP 6 - - - - - - - - - - - - - - - - - - - The class-loading element is no longer valid in the jboss-web.xml file. - - - - - - - - ----- -[] - -[id="mta-installing-rule-in-directory_{context}"] -== Installing the rule - -An {ProductShortName} rule is installed by placing the rule into the appropriate directory. - -Copy the `JBoss5-web-class-loading.windup.xml` file to the `<{ProductShortName}_HOME>/rules/` directory. - -[source,options="nowrap",subs="attributes+"] ----- -$ cp /home//migration-rules/rules/JBoss5-web-class-loading.windup.xml <{ProductShortName}_HOME>/rules/ ----- -[] - -[id="mta-testing-the-rule_{context}"] -== Testing the rule - -Open a terminal and run the following command, passing the test file as an input argument and a directory for the output report. - -[options="nowrap",subs="attributes+"] ----- -$ <{ProductShortName}_HOME>/bin/{mta-cli} --sourceMode --input /home//migration-rules/data --output /home//migration-rules/reports --target eap:6 ----- - -You should see the following result. - -[options="nowrap",subs="attributes+"] ----- -Report created: /home//migration-rules/reports/index.html - Access it at this URL: file:///home//migration-rules/reports/index.html ----- -[] -[id="mta-reviewing-the-report_{context}"] -== Reviewing the reports - -Review the report to be sure that it provides the expected results. For a more detailed walkthrough of {ProductShortName} reports, see the link:{ProductDocUserGuideURL}#review-reports_cli-guide[Reviewing the reports] section of the {ProductShortName} _{UserCLIBookName}_. - -. Open `/home//migration-rules/reports/index.html` in a web browser. -. Verify that the rule ran successfully. -.. From the main landing page, click the *Rule providers execution overview* link to open the Rule Providers Execution Overview. -+ -.. Find the `JBoss5-web-class-loading_001` rule and verify that its *Status?* is `Condition met` and its *Result?* is `success`. -+ -.Test rule execution -image::executed-test-rule.png[Test rule execution] -. Verify that the rule matches the test data: - -.. From the main landing page, click the name of the application or input folder, which is `data` in this example. -.. Click the *Application Details* report link. -.. Click the *jboss-web.xml* link to view the *Source Report*. -+ -You can see that the `` line is highlighted, and the hint from the custom rule is shown inline. -+ -.Rule match -image::test-rule-details.png[Rule match] -+ -// TODO: Consider updating with test data/rule combo that won't match on any of the other existing rules. -The top of the file lists the classifications for matching rules. You can use the link icon to view the details for that rule. Notice that in this example, the `jboss-web.xml` file matched on another rule (`JBoss web application descriptor (jboss-web.xml)`) that produced `1` story point. This story point, combined with the `1` story point from our custom rule, brings the total story points for this file to `2`. From 7c5ce6ac5e58362bc9a71897602cf53807d90512 Mon Sep 17 00:00:00 2001 From: Eli Marcus Date: Mon, 5 Feb 2024 18:34:03 +0200 Subject: [PATCH 3/6] Delete docs/topics/vs-code-extension-run-configuration.adoc seems to be causing a merge conflict --- .../vs-code-extension-run-configuration.adoc | 32 ------------------- 1 file changed, 32 deletions(-) delete mode 100644 docs/topics/vs-code-extension-run-configuration.adoc diff --git a/docs/topics/vs-code-extension-run-configuration.adoc b/docs/topics/vs-code-extension-run-configuration.adoc deleted file mode 100644 index 009a1a1187..0000000000 --- a/docs/topics/vs-code-extension-run-configuration.adoc +++ /dev/null @@ -1,32 +0,0 @@ -// Module included in the following assemblies: -// -// * docs/vsc-extension-guide/master.adoc - -:_content-type: PROCEDURE -[id="vs-code-extension-run-configuration_{context}"] -= Configuring a run configuration - -You can configure multiple run configurations to run against each project you import to VS Code. - -.Prerequisites - -* `{mta-cli}` executable installed. You can download the `{mta-cli}` executable from link:{DevDownloadPageURL}[{LC_PSN} download]. - -.Procedure - -. In *Extensions* view, click the {ProductName} icon (image:vs_extension_icon.png[{ProductShortName} code extension]) on the Activity bar. -. Click the *+* (plus sign) next to *{ProductName}* to add a run configuration. -. Complete the following configuration fields: - -** *Name*: Enter a meaningful name for the analysis configuration or accept the default. -** *cli*: Enter the path to the cli executable. For example: `$HOME/{LC_PSN}-cli-{ProductDistributionVersion}/bin/{mta-cli}`. -** *Input*: Set to the path of the project that you have open within your IDE by clicking *Add* and doing one of the following: - -*** Enter the input file or directory and press Enter. -*** Click *Open File Explorer* and select the directory. - -** *Target*: Select one or more target migration paths. - -. Right-click the run configuration and select *Run*. -+ -When the analysis is completed, you can click the *Open Report* button to open the {ProductShortName} report, which describes any issues you need to address before you migrate or modernize your application. For more information, see link:{ProductDocUserGuideURL}#review-reports_cli-guide[Reviewing the reports] in the _{UserCLIBookName}_. From 4303b89a1bad75e4fa94722c4d01a36881e1fef2 Mon Sep 17 00:00:00 2001 From: emarcusRH Date: Tue, 6 Feb 2024 16:50:19 +0200 Subject: [PATCH 4/6] adding analyze to mta-cli analysis commands --- docs/topics/cli-run.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/topics/cli-run.adoc b/docs/topics/cli-run.adoc index 87f7f6588a..575aa29dd0 100644 --- a/docs/topics/cli-run.adoc +++ b/docs/topics/cli-run.adoc @@ -38,7 +38,7 @@ The following command analyzes the `com.acme` and `org.apache` packages of the l [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/{mta-cli} \ +$ <{ProductShortName}_HOME>/bin/{mta-cli} analyze \ --input /path/to/jee-example-app-1.0.0.ear \ --output /path/to/report-output/ --source eap:5 --target eap:7 \ --packages com.acme org.apache @@ -52,7 +52,7 @@ The following command analyzes the `org.jboss.seam` packages of the link:https:/ [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/{mta-cli} --sourceMode --input /path/to/seam-booking-5.2/ \ +$ <{ProductShortName}_HOME>/bin/{mta-cli} analyze --sourceMode --input /path/to/seam-booking-5.2/ \ --output /path/to/report-output/ --target eap:6 --packages org.jboss.seam ---- [] @@ -63,7 +63,7 @@ The following command analyzes the `com.acme` and `org.apache` packages of the l [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/{mta-cli} --input /path/to/jee-example-app-1.0.0.ear \ +$ <{ProductShortName}_HOME>/bin/{mta-cli} analyze --input /path/to/jee-example-app-1.0.0.ear \ --output /path/to/report-output/ \ --target eap:7 --target cloud-readiness --packages com.acme org.apache ---- From b81a3e9c25a205e1b8b530d9f4333a51a9ca1251 Mon Sep 17 00:00:00 2001 From: emarcusRH Date: Wed, 7 Feb 2024 17:33:03 +0200 Subject: [PATCH 5/6] updates to mta-cli analyze commands --- docs/topics/cli-run.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/topics/cli-run.adoc b/docs/topics/cli-run.adoc index 575aa29dd0..77c36d1b71 100644 --- a/docs/topics/cli-run.adoc +++ b/docs/topics/cli-run.adoc @@ -15,7 +15,7 @@ You can run {ProductShortName} against your application. + [source,terminal,subs="attributes+"] ---- -$ ./{mta-cli} --input /path/to/jee-example-app-1.0.0.ear \ +$ ./{mta-cli} analyze --input /path/to/jee-example-app-1.0.0.ear \ --output /path/to/output --source weblogic --target eap:6 \ --packages com.acme org.apache ---- @@ -52,7 +52,7 @@ The following command analyzes the `org.jboss.seam` packages of the link:https:/ [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/{mta-cli} analyze --sourceMode --input /path/to/seam-booking-5.2/ \ +$ <{ProductShortName}_HOME>/bin/{mta-cli} analyze --mode --input /path/to/seam-booking-5.2/ \ --output /path/to/report-output/ --target eap:6 --packages org.jboss.seam ---- [] From 7915aaae5099f78e2cc9d7f052fead406a6e85a6 Mon Sep 17 00:00:00 2001 From: emarcusRH Date: Thu, 8 Feb 2024 19:27:53 +0200 Subject: [PATCH 6/6] updates to mta-cli analyze commands --- docs/topics/cli-run.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/cli-run.adoc b/docs/topics/cli-run.adoc index 77c36d1b71..af975df920 100644 --- a/docs/topics/cli-run.adoc +++ b/docs/topics/cli-run.adoc @@ -52,7 +52,7 @@ The following command analyzes the `org.jboss.seam` packages of the link:https:/ [source,terminal,subs="attributes+"] ---- -$ <{ProductShortName}_HOME>/bin/{mta-cli} analyze --mode --input /path/to/seam-booking-5.2/ \ +$ <{ProductShortName}_HOME>/bin/{mta-cli} analyze --mode source-only --input /path/to/seam-booking-5.2/ \ --output /path/to/report-output/ --target eap:6 --packages org.jboss.seam ---- []