Commit from GitHub Actions (WildFly Quickstarts Update 'README.adoc's)

wildfly · Nov 12, 2024 · f525d3f · f525d3f
1 parent 3eb56b9
commit f525d3f
Show file tree

Hide file tree

Showing 11 changed files with 132 additions and 22 deletions.
diff --git a/helloworld/README.adoc b/helloworld/README.adoc
@@ -763,7 +763,7 @@ endif::mavenServerProvisioningCommand[]
 
 You can use the WildFly Maven Plugin to build a {productName} bootable JAR to run this quickstart.
 
-The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which configures the bootable JAR building:
+The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `<bootable-jar>true</bootable-jar>` configuration element:
 
 [source,xml,subs="attributes+"]
 ----
@@ -798,7 +798,7 @@ The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, whi
       </profile>
 ----
 
-The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar may be found at `target/{artifactId}-bootable.jar`
+The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar file is named `{artifactId}-bootable.jar`, and may be found in the `target` directory.
 
 .Procedure
 
@@ -815,6 +815,15 @@ $ mvn clean {mavenServerProvisioningCommand}
 ----
 $ mvn wildfly:start-jar
 ----
++
+[NOTE]
+====
+You may also start the bootable jar without Maven, using the `java` command.
+[source,subs="attributes+",options="nowrap"]
+----
+$ java -jar target/{artifactId}-bootable.jar
+----
+====
 
 . Run the integration tests use the `verify` goal, with the `integration-testing` profile activated.
 +
@@ -830,6 +839,7 @@ $ mvn verify -Pintegration-testing
 $ mvn wildfly:shutdown
 ----
 
+
 :leveloffset!:
 // OpenShift
 :leveloffset: +1

diff --git a/micrometer/README.adoc b/micrometer/README.adoc
@@ -1120,7 +1120,7 @@ endif::mavenServerProvisioningCommand[]
 
 You can use the WildFly Maven Plugin to build a {productName} bootable JAR to run this quickstart.
 
-The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which configures the bootable JAR building:
+The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `<bootable-jar>true</bootable-jar>` configuration element:
 
 [source,xml,subs="attributes+"]
 ----
@@ -1155,7 +1155,7 @@ The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, whi
       </profile>
 ----
 
-The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar may be found at `target/{artifactId}-bootable.jar`
+The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar file is named `{artifactId}-bootable.jar`, and may be found in the `target` directory.
 
 .Procedure
 
@@ -1172,6 +1172,15 @@ $ mvn clean {mavenServerProvisioningCommand}
 ----
 $ mvn wildfly:start-jar
 ----
++
+[NOTE]
+====
+You may also start the bootable jar without Maven, using the `java` command.
+[source,subs="attributes+",options="nowrap"]
+----
+$ java -jar target/{artifactId}-bootable.jar
+----
+====
 
 . Run the integration tests use the `verify` goal, with the `integration-testing` profile activated.
 +
@@ -1187,6 +1196,7 @@ $ mvn verify -Pintegration-testing
 $ mvn wildfly:shutdown
 ----
 
+
 :leveloffset!:
 // OpenShift
 :leveloffset: +1

diff --git a/microprofile-config/README.adoc b/microprofile-config/README.adoc
@@ -1447,7 +1447,7 @@ endif::mavenServerProvisioningCommand[]
 
 You can use the WildFly Maven Plugin to build a {productName} bootable JAR to run this quickstart.
 
-The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which configures the bootable JAR building:
+The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `<bootable-jar>true</bootable-jar>` configuration element:
 
 [source,xml,subs="attributes+"]
 ----
@@ -1482,7 +1482,7 @@ The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, whi
       </profile>
 ----
 
-The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar may be found at `target/{artifactId}-bootable.jar`
+The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar file is named `{artifactId}-bootable.jar`, and may be found in the `target` directory.
 
 .Procedure
 
@@ -1499,6 +1499,15 @@ $ mvn clean {mavenServerProvisioningCommand}
 ----
 $ mvn wildfly:start-jar
 ----
++
+[NOTE]
+====
+You may also start the bootable jar without Maven, using the `java` command.
+[source,subs="attributes+",options="nowrap"]
+----
+$ java -jar target/{artifactId}-bootable.jar
+----
+====
 
 . Run the integration tests use the `verify` goal, with the `integration-testing` profile activated.
 +
@@ -1514,6 +1523,7 @@ $ mvn verify -Pintegration-testing
 $ mvn wildfly:shutdown
 ----
 
+
 :leveloffset!:
 
 // Openshift

diff --git a/microprofile-fault-tolerance/README.adoc b/microprofile-fault-tolerance/README.adoc
@@ -1269,7 +1269,7 @@ endif::mavenServerProvisioningCommand[]
 
 You can use the WildFly Maven Plugin to build a {productName} bootable JAR to run this quickstart.
 
-The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which configures the bootable JAR building:
+The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `<bootable-jar>true</bootable-jar>` configuration element:
 
 [source,xml,subs="attributes+"]
 ----
@@ -1304,7 +1304,7 @@ The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, whi
       </profile>
 ----
 
-The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar may be found at `target/{artifactId}-bootable.jar`
+The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar file is named `{artifactId}-bootable.jar`, and may be found in the `target` directory.
 
 .Procedure
 
@@ -1321,6 +1321,15 @@ $ mvn clean {mavenServerProvisioningCommand}
 ----
 $ mvn wildfly:start-jar
 ----
++
+[NOTE]
+====
+You may also start the bootable jar without Maven, using the `java` command.
+[source,subs="attributes+",options="nowrap"]
+----
+$ java -jar target/{artifactId}-bootable.jar
+----
+====
 
 . Run the integration tests use the `verify` goal, with the `integration-testing` profile activated.
 +
@@ -1336,6 +1345,7 @@ $ mvn verify -Pintegration-testing
 $ mvn wildfly:shutdown
 ----
 
+
 :leveloffset!:
 
 // OpenShift

diff --git a/microprofile-health/README.adoc b/microprofile-health/README.adoc
@@ -1100,7 +1100,7 @@ endif::mavenServerProvisioningCommand[]
 
 You can use the WildFly Maven Plugin to build a {productName} bootable JAR to run this quickstart.
 
-The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which configures the bootable JAR building:
+The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `<bootable-jar>true</bootable-jar>` configuration element:
 
 [source,xml,subs="attributes+"]
 ----
@@ -1135,7 +1135,7 @@ The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, whi
       </profile>
 ----
 
-The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar may be found at `target/{artifactId}-bootable.jar`
+The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar file is named `{artifactId}-bootable.jar`, and may be found in the `target` directory.
 
 .Procedure
 
@@ -1152,6 +1152,15 @@ $ mvn clean {mavenServerProvisioningCommand}
 ----
 $ mvn wildfly:start-jar
 ----
++
+[NOTE]
+====
+You may also start the bootable jar without Maven, using the `java` command.
+[source,subs="attributes+",options="nowrap"]
+----
+$ java -jar target/{artifactId}-bootable.jar
+----
+====
 
 . Run the integration tests use the `verify` goal, with the `integration-testing` profile activated.
 +
@@ -1167,6 +1176,7 @@ $ mvn verify -Pintegration-testing
 $ mvn wildfly:shutdown
 ----
 
+
 :leveloffset!:
 
 // OpenShift

diff --git a/microprofile-jwt/README.adoc b/microprofile-jwt/README.adoc
@@ -1309,7 +1309,7 @@ endif::mavenServerProvisioningCommand[]
 
 You can use the WildFly Maven Plugin to build a {productName} bootable JAR to run this quickstart.
 
-The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which configures the bootable JAR building:
+The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `<bootable-jar>true</bootable-jar>` configuration element:
 
 [source,xml,subs="attributes+"]
 ----
@@ -1344,7 +1344,7 @@ The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, whi
       </profile>
 ----
 
-The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar may be found at `target/{artifactId}-bootable.jar`
+The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar file is named `{artifactId}-bootable.jar`, and may be found in the `target` directory.
 
 .Procedure
 
@@ -1361,6 +1361,15 @@ $ mvn clean {mavenServerProvisioningCommand}
 ----
 $ mvn wildfly:start-jar
 ----
++
+[NOTE]
+====
+You may also start the bootable jar without Maven, using the `java` command.
+[source,subs="attributes+",options="nowrap"]
+----
+$ java -jar target/{artifactId}-bootable.jar
+----
+====
 
 . Run the integration tests use the `verify` goal, with the `integration-testing` profile activated.
 +
@@ -1376,6 +1385,7 @@ $ mvn verify -Pintegration-testing
 $ mvn wildfly:shutdown
 ----
 
+
 :leveloffset!:
 
 // OpenShift

diff --git a/microprofile-lra/README.adoc b/microprofile-lra/README.adoc
@@ -936,7 +936,7 @@ endif::mavenServerProvisioningCommand[]
 
 You can use the WildFly Maven Plugin to build a {productName} bootable JAR to run this quickstart.
 
-The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which configures the bootable JAR building:
+The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `<bootable-jar>true</bootable-jar>` configuration element:
 
 [source,xml,subs="attributes+"]
 ----
@@ -971,7 +971,7 @@ The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, whi
       </profile>
 ----
 
-The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar may be found at `target/{artifactId}-bootable.jar`
+The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar file is named `{artifactId}-bootable.jar`, and may be found in the `target` directory.
 
 .Procedure
 
@@ -988,6 +988,15 @@ $ mvn clean {mavenServerProvisioningCommand}
 ----
 $ mvn wildfly:start-jar
 ----
++
+[NOTE]
+====
+You may also start the bootable jar without Maven, using the `java` command.
+[source,subs="attributes+",options="nowrap"]
+----
+$ java -jar target/{artifactId}-bootable.jar
+----
+====
 
 . Run the integration tests use the `verify` goal, with the `integration-testing` profile activated.
 +
@@ -1003,6 +1012,7 @@ $ mvn verify -Pintegration-testing
 $ mvn wildfly:shutdown
 ----
 
+
 :leveloffset!:
 
 // OpenShift

diff --git a/microprofile-openapi/README.adoc b/microprofile-openapi/README.adoc
@@ -724,7 +724,7 @@ endif::mavenServerProvisioningCommand[]
 
 You can use the WildFly Maven Plugin to build a {productName} bootable JAR to run this quickstart.
 
-The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which configures the bootable JAR building:
+The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `<bootable-jar>true</bootable-jar>` configuration element:
 
 [source,xml,subs="attributes+"]
 ----
@@ -759,7 +759,7 @@ The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, whi
       </profile>
 ----
 
-The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar may be found at `target/{artifactId}-bootable.jar`
+The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar file is named `{artifactId}-bootable.jar`, and may be found in the `target` directory.
 
 .Procedure
 
@@ -776,6 +776,15 @@ $ mvn clean {mavenServerProvisioningCommand}
 ----
 $ mvn wildfly:start-jar
 ----
++
+[NOTE]
+====
+You may also start the bootable jar without Maven, using the `java` command.
+[source,subs="attributes+",options="nowrap"]
+----
+$ java -jar target/{artifactId}-bootable.jar
+----
+====
 
 . Run the integration tests use the `verify` goal, with the `integration-testing` profile activated.
 +
@@ -791,6 +800,7 @@ $ mvn verify -Pintegration-testing
 $ mvn wildfly:shutdown
 ----
 
+
 :leveloffset!:
 
 // OpenShift

diff --git a/microprofile-reactive-messaging-kafka/README.adoc b/microprofile-reactive-messaging-kafka/README.adoc
@@ -1615,7 +1615,7 @@ endif::mavenServerProvisioningCommand[]
 
 You can use the WildFly Maven Plugin to build a {productName} bootable JAR to run this quickstart.
 
-The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which configures the bootable JAR building:
+The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `<bootable-jar>true</bootable-jar>` configuration element:
 
 [source,xml,subs="attributes+"]
 ----
@@ -1650,7 +1650,7 @@ The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, whi
       </profile>
 ----
 
-The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar may be found at `target/{artifactId}-bootable.jar`
+The *bootable-jar* profile is activate by default, and when built the {productName} bootable jar file is named `{artifactId}-bootable.jar`, and may be found in the `target` directory.
 
 .Procedure
 
@@ -1667,6 +1667,15 @@ $ mvn clean {mavenServerProvisioningCommand}
 ----
 $ mvn wildfly:start-jar
 ----
++
+[NOTE]
+====
+You may also start the bootable jar without Maven, using the `java` command.
+[source,subs="attributes+",options="nowrap"]
+----
+$ java -jar target/{artifactId}-bootable.jar
+----
+====
 
 . Run the integration tests use the `verify` goal, with the `integration-testing` profile activated.
 +
@@ -1682,6 +1691,7 @@ $ mvn verify -Pintegration-testing
 $ mvn wildfly:shutdown
 ----
 
+
 :leveloffset!:
 
 [NOTE]