MTA- : Removing discrete headers

Signed-off-by: A.Arnold <[email protected]>

Author: anarnold97

docs/cli-guide/master.adoc

@@ -66,11 +66,11 @@ include::topics/mta-cli-run-single-app.adoc[leveloffset=+3]
 
 include::topics/mta-cli-run-multiple-apps.adoc[leveloffset=+3]
 
+include::topics/proc_running-the-containerless-mta-cli.adoc[leveloffset=+3]
+
 // Analyze application source code
 include::topics/mta-cli-analyze.adoc[leveloffset=+3]
 
-include::topics/proc_running-the-containerless-mta-cli.adoc[leveloffset=+3]
-
 // Transform XML rules to YAML
 include::topics/mta-cli-transform.adoc[leveloffset=+3]
 
@@ -104,6 +104,9 @@ include::topics/mta-review-reports.adoc[leveloffset=+1]
 // Optimize {ProductShortName} Performance
 include::topics/mta-optimize-performance.adoc[leveloffset=+1]
 
+// Issues with reports
+include::topics/issues-with-report.adoc[leveloffset=+2]
+
 // Configure {ProductShortName} to Exclude Files and Packages
 // include::topics/mta-exclude-files-and-packages.adoc[leveloffset=+2]
 

docs/topics/cli-run.adoc

@@ -8,8 +8,7 @@
 
 You can configure the {WebName} to require authentication for access. To  enable authentication, you have to install Red Hat Single Sign-On (SSO).
 
-[discrete]
-[id="enabling-authentication_{context}"]
+[id="mta-enabling-authentication_{context}"]
 == Enabling authentication
 
 .Procedure
@@ -86,7 +85,6 @@ C:\<MTR_HOME>\run_windup.bat
 ----
 . Open the browser at `\http://localhost:8080/windup-ui`.
 
-[discrete]
 [id="disabling-authentication_{context}"]
 == Disabling authentication
 

docs/topics/configuring-web-console-authentication-for-linux-windows-macos.adoc

@@ -29,7 +29,8 @@ The CSV files are exported to the directory specified by the `outputDirectory` a
 endif::maven-guide[]
 
 ifdef::cli-guide[]
-[discrete]
+
+[id="access-report-from-app-report_{context}"]
 === Accessing the report from the application report
 
 If you have exported the CSV report, you can download all of the CSV issues in the Issues Report. To download these issues, click *Download All Issues CSV* in the Issues Report.
@@ -38,13 +39,15 @@ If you have exported the CSV report, you can download all of the CSV issues in t
 image::4-1-issues-report-with-csv-download.png[Issues report with CSV download]
 endif::cli-guide[]
 
+[id="import-csv-file-spreadsheet_{context}"]
 == Importing the CSV file into a spreadsheet program
 
 . Launch the spreadsheet software, for example, Microsoft Excel.
 . Choose *File* -> *Open*.
 . Browse to the CSV exported file and select it.
 . The data is now ready to analyze in the spreadsheet software.
 
+[id="about-csv-data-strcture_{context}"]
 == About the CSV data structure
 
 The CSV formatted output file contains the following data fields:

docs/topics/csv-export.adoc

@@ -25,11 +25,10 @@ $ ./{LC_PSN}-cli --input /path/to/jee-example-app-1.0.0.ear --output /path/to/ou
 
 . Access the report.
 
-[discrete]
 [id="command-examples_{context}"]
 == {ProductShortName} Command examples
 
-[discrete]
+[id="running-mta-application-archive_{context}"]
 === Running {ProductShortName} on an application archive
 
 The following command analyzes the `com.acme` and `org.apache` packages of the link:https://github.com/windup/windup/blob/master/test-files/jee-example-app-1.0.0.ear[jee-example-app-1.0.0.ear] example EAR archive for migrating from JBoss EAP 5 to JBoss EAP 7:
@@ -39,7 +38,7 @@ The following command analyzes the `com.acme` and `org.apache` packages of the l
 $ <{ProductShortName}_HOME>/bin/{LC_PSN}-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
 ----
 
-[discrete]
+[id="running-mta-on-source-code_{context}"]
 === Running {ProductShortName} on source code
 
 The following command analyzes the `org.jboss.seam` packages of the link:https://github.com/windup/windup/tree/master/test-files/seam-booking-5.2[seam-booking-5.2] example source code for migrating to JBoss EAP 6.
@@ -49,7 +48,7 @@ The following command analyzes the `org.jboss.seam` packages of the link:https:/
 $ <{ProductShortName}_HOME>/bin/{LC_PSN}-cli --sourceMode --input /path/to/seam-booking-5.2/ --output /path/to/report-output/ --target eap:6 --packages org.jboss.seam
 ----
 
-[discrete]
+[id="running-mta-cloud-readiness-rules_{context}"]
 === Running cloud-readiness rules
 
 The following command analyzes the `com.acme` and `org.apache` packages of the link:https://github.com/windup/windup/blob/master/test-files/jee-example-app-1.0.0.ear[jee-example-app-1.0.0.ear] example EAR archive for migrating to JBoss EAP 7. It also evaluates for cloud readiness:
@@ -59,7 +58,7 @@ The following command analyzes the `com.acme` and `org.apache` packages of the l
 $ <{ProductShortName}_HOME>/bin/{LC_PSN}-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
 ----
 
-[discrete]
+[id="overriding-mta-product-properties_{context}"]
 === Overriding {ProductShortName} properties
 
 To override the default _Fernflower_ decompiler, pass the `-Dwindup.decompiler` argument on the command line. For example, to use the _Procyon_ decompiler, use the following syntax:
@@ -69,7 +68,6 @@ To override the default _Fernflower_ decompiler, pass the `-Dwindup.decompiler`
 $ <{ProductShortName}_HOME>/bin/{LC_PSN}-cli -Dwindup.decompiler=procyon --input <INPUT_ARCHIVE_OR_DIRECTORY> --output <OUTPUT_REPORT_DIRECTORY> --target <TARGET_TECHNOLOGY> --packages <PACKAGE_1> <PACKAGE_2>
 ----
 
-[discrete]
 [id="cli-bash-completion_{context}"]
 == About {ProductShortName} {CLINameTitle} Bash completion
 
@@ -80,7 +78,6 @@ The {ProductShortName} {CLIName} provides an option to enable Bash completion fo
 $ <{ProductShortName}_HOME>/bin/{LC_PSN}-cli [TAB]
 ----
 
-[discrete]
 [id="bash-completion-temporary_{context}"]
 === Enabling Bash completion
 
@@ -91,7 +88,6 @@ To enable Bash completion for the current shell, execute the following command:
 $ source <{ProductShortName}_HOME>/bash-completion/{LC_PSN}-cli
 ----
 
-[discrete]
 [id="bash-completion-persistent_{context}"]
 === Enabling persistent Bash completion
 
@@ -111,7 +107,6 @@ source <{ProductShortName}_HOME>/bash-completion/{LC_PSN}-cli
 # cp <{ProductShortName}_HOME>/bash-completion/{LC_PSN}-cli /etc/bash_completion.d/
 ----
 
-[discrete]
 [id="accessing-help_{context}"]
 == Accessing {ProductShortName} help
 

docs/topics/execute.adoc

@@ -0,0 +1,17 @@
+// Module included in the following assemblies:
+//
+// * docs/cli-guide/master.adoc
+
+:_content-type: CONCEPT
+[id="issues-with-report_{context}"]
+= Issues with reports
+
+.Running {ProductShortName} on a project with an inaccessible parent pom.xml file may not result in a full analysis
+
+Running {ProductFullName} on a project with an inaccessible parent pom.xml file may not result in a full analysis. For example, this issue impacts the link:https://github.com/jboss-developer/jboss-eap-quickstarts/tree/EAP_7.4.0.GA[JBoss EAP Quickstarts], which demonstrate JBoss EAP, Jakarta EE 10, and other additional technologies. They provide small, specific, working examples that can be used as a reference for your project. However, these quickstarts specify a relative path to their parent POM file, which does not exist when the {ProductShortName} container is run.
+
+Specifying an input path of link:https://github.com/jboss-developer/jboss-eap-quickstarts/tree/EAP_7.4.0.GA/kitchensink[`kitchensink`] mounts the `kitchensink` directory as a volume in the container, but that means that the JDT Language Server (jdtls) is unable to access the parent link:https://github.com/jboss-developer/jboss-eap-quickstarts/blob/EAP_7.4.0.GA/kitchensink/pom.xml[pom.xml] file.
+
+This causes the jdtls to encounter a `Non-resolvable parent POM for org.jboss.eap.quickstarts:kitchensink:7.4.0.GA error` project build error. This error creates a `.project` file, which is missing the `org.eclipse.jdt.core.javanature`, meaning that jdtls, and subsequently {ProductShortName}, is unable to access details about the Java files.
+
+If you remove the parent pom.xml file and make the `kitchensink` project completely standalone, there are no issues.

docs/topics/issues-with-report.adoc

@@ -51,7 +51,6 @@ The example `jee-example-app-1.0.0.ear` application is an EAR archive that conta
 Review each of the generated files and customize as appropriate for your project. To learn more about Maven POM files, see the link:https://maven.apache.org/guides/introduction/introduction-to-the-pom.html[Introduction to the POM] section of the Apache Maven documentation.
 
 [id="root-pom-file_{context}"]
-[discrete]
 === Root POM file
 
 The root POM file for the `jee-example-app-1.0.0.ear` application can be found at `/path/to/output/mavenized/jee-example-app/pom.xml`. This file identifies the directories for all of the project modules.
@@ -76,7 +75,6 @@ The root POM is also configured to use the link:https://maven.repository.redhat.
 
 
 [id="bom-file_{context}"]
-[discrete]
 === BOM file
 
 The Bill of Materials (BOM) file is generated in the directory ending in `-bom`. For the example `jee-example-app-1.0.0.ear` application, the BOM file can be found at `/path/to/output/mavenized/jee-example-app/jee-example-app-bom/pom.xml`. The purpose of this BOM is to have the versions of third-party dependencies used by the project defined in one place. For more information on using a BOM, see the link:https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html[Introduction to the dependency mechanism] section of the Apache Maven documentation.
@@ -102,7 +100,6 @@ The following dependencies are listed in the BOM for the example `jee-example-ap
 ----
 
 [id="app-pom-files_{context}"]
-[discrete]
 === Application POM files
 
 Each application module that can be mavenized has a separate directory containing its POM file. The directory name contains the name of the archive and ends in a `-jar`, `-war`, or `-ear` suffix, depending on the archive type.

docs/topics/mavenize.adoc

@@ -31,7 +31,7 @@ $ ./{mta-cli} analyze --input <path_to_input> \
 [id="command-examples_{context}"]
 == {ProductShortName} command examples
 
-[discrete]
+[id="running-mta-cli-single-app-archive_{context}"]
 === Running {ProductShortName} on an application archive
 
 The following command analyzes the example EAR archive named `jee-example-app-1.0.0.ear` for migrating from JBoss EAP 5 to JBoss EAP 7:
@@ -44,7 +44,7 @@ $ <{ProductShortName}_HOME>/{mta-cli} analyze \
 ----
 []
 
-[discrete]
+[id="running-mta-cli-single-source-code_{context}"]
 === Running {ProductShortName} on source code
 
 The following command analyzes the source code of an example application called `customer-management` for migrating to JBoss EAP 8.
@@ -56,7 +56,8 @@ $ <{ProductShortName}_HOME>/{mta-cli} analyze --mode source-only --input <path_t
 --output <path_to_report_output> --target eap8
 ----
 []
-[discrete]
+
+[id="running-mta-cli-single-cloud-readiness_{context}"]
 === Running cloud-readiness rules
 
 The following command analyzes the example EAR archive named `jee-example-app-1.0.0.ear` for migrating to JBoss EAP 7. It also evaluates the archive for cloud readiness: