Skip to content

Commit b4a4325

Browse files
committed
Resolved the conflict
2 parents 8bb04d1 + 18d5dd7 commit b4a4325

34 files changed

+404
-107
lines changed

docs/cli-guide/master.adoc

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
:mta:
22
include::topics/templates/document-attributes.adoc[]
3-
:_content-type: ASSEMBLY
3+
:_mod-docs-content-type: ASSEMBLY
44
[id="cli-guide"]
55
= CLI Guide
66

@@ -37,8 +37,24 @@ include::topics/installing-cli-tool.adoc[leveloffset=+2]
3737
// CLI known issues
3838
include::topics/cli-tool-known-issues.adoc[leveloffset=+3]
3939

40+
[id="running-cli"]
41+
=== Running the CLI
42+
43+
You can run the {ProductFullName} {CLINameTitle} against one or more applications.
44+
45+
Before {ProductShortName} 7.1.0, if you wanted to run the {CLINameTitle} against multiple applications, you ran a series of `--analyze` commands, each against an application, and each generating a separate report. This option, which is still fully supported, is described in xref:mta-cli-run-single-app_cli-guide[Running the {ProductShortName} {CLINameTitle} against an application].
46+
47+
In {ProductShortName} 7.1.0 and later, you can run the {CLINameTitle} against multiple applications by using the `--bulk` option, to generate a single report. This option, which is presented as a Developer Preview, is described in xref:mta-cli-run-multiple-apps_cli-guide[Running the {ProductShortName} {CLINameTitle} against multiple applications and generating a single report (Developer Preview)].
48+
49+
[IMPORTANT]
50+
====
51+
include::snippets/developer-preview.adoc[]
52+
====
53+
4054
// Run the CLI
41-
include::topics/mta-cli-run.adoc[leveloffset=+2]
55+
include::topics/mta-cli-run-single-app.adoc[leveloffset=+3]
56+
57+
include::topics/mta-cli-run-multiple-apps.adoc[leveloffset=+3]
4258

4359
// Analyze application source code
4460
include::topics/mta-cli-analyze.adoc[leveloffset=+3]

docs/cli-guide/snippets

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../snippets
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../snippets

docs/getting-started-guide/snippets

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../snippets
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../snippets

docs/maven-guide/snippets

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../snippets

docs/release-notes/snippets

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../snippets

docs/rules-development-guide/snippets

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../snippets

docs/topics/create-first-yaml-rule.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
//
33
// * docs/rules-development-guide/master.adoc
44

5-
:_content-type: PROCEDURE
5+
:_mod-docs-content-type: PROCEDURE
66
[id="create-first-yaml-rule_{context}"]
77
= Creating your first YAML rule
88

@@ -13,7 +13,7 @@ In this example, you will create a rule to discover instances where an applicati
1313
[id="creating-yaml-file-for-the-rule_{context}"]
1414
== Creating a YAML file for the rule
1515

16-
Create a YAML file for your first rule.
16+
* Create a YAML file for your first rule.
1717

1818
[options="nowrap",subs="attributes+"]
1919
----
@@ -82,7 +82,7 @@ when(condition)
8282

8383
.Procedure
8484

85-
. In the `rule.yaml` file you created, paste the following contents:
85+
* In the `rule.yaml` file you created, paste the following contents:
8686
+
8787
[options="nowrap",subs="attributes+"]
8888
----
@@ -97,10 +97,10 @@ when(condition)
9797
- <LINKS> <7>
9898
----
9999
+
100-
<1> Unique ID for your rule, for instance, `jboss5-web-class-loading`.
100+
<1> Unique ID for your rule. For example, `jboss5-web-class-loading`.
101101
<2> Text description of the rule.
102102
<3> Complete the `when` block specifying one or more conditions:
103-
.. Use the `builtin` providers XML capability because this rule checks for a match in an XML file.
103+
.. Use the `builtin` provider's XML capability because this rule checks for a match in an XML file.
104104
.. To match on the `class-loading` element that is a child of `jboss-web`, use the XPath expression `jboss-web/web-loading` as an XML query. In this case, you need just one condition:
105105
+
106106
[options="nowrap",subs="attributes+"]
@@ -146,7 +146,7 @@ The rule is now complete and looks similar to the following:
146146
== Installing the rule
147147

148148
.Procedure
149-
. Point the CLI to the rule file you created :
149+
* Point the CLI to the rule file you created :
150150
+
151151
[options="nowrap",subs="attributes+"]
152152
----

docs/topics/create-yaml-rule.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
//
33
// * docs/rules-development-guide/master.adoc
44

5-
:_content-type: PROCEDURE
5+
:_mod-docs-content-type: PROCEDURE
66
[id="create-yaml-rule_{context}"]
77
= Creating a YAML rule
88

@@ -125,7 +125,7 @@ The table below lists all available providers, their capabilities, and their fie
125125
|Yes
126126
|Finds files with names matching this pattern
127127
|`hasTags`
128-
3+>|This is an inline list of string tags. See _Tag Action_ for details on tag format.
128+
3+^| This is an inline list of string tags. See *Tag Actions* in xref:yaml-rule-actions_{context}[Rule Actions] for details on tag format.
129129

130130
.5+.^|`go`
131131
|`referenced`

0 commit comments

Comments
 (0)