diff --git a/shared-doc/build-and-run-the-quickstart-with-bootable-jar.adoc b/shared-doc/build-and-run-the-quickstart-with-bootable-jar.adoc
index 31c6f6cdd5..4e32d992e1 100644
--- a/shared-doc/build-and-run-the-quickstart-with-bootable-jar.adoc
+++ b/shared-doc/build-and-run-the-quickstart-with-bootable-jar.adoc
@@ -19,40 +19,84 @@ You can use the WildFly Maven Plugin to build a {productName} bootable JAR to ru
The quickstart `pom.xml` file contains a Maven profile named *bootable-jar*, which activates the bootable JAR packaging when provisioning {productName}, through the `true` configuration element:
+ifndef::ProductRelease[]
[source,xml,subs="attributes+"]
----
-
- bootable-jar
-
- true
-
-
-
-
- org.wildfly.plugins
- wildfly-maven-plugin
-
-
- ${version.server}
-
- true
- ...
-
-
-
-
- package
-
-
-
-
- ...
-
-
-
+
+ bootable-jar
+
+ true
+
+
+
+
+ org.wildfly.plugins
+ wildfly-maven-plugin
+
+
+ ${version.server}
+
+ true
+ ...
+
+
+
+
+ package
+
+
+
+
+ ...
+
+
+
----
+endif::[]
+ifdef::ProductRelease[]
+[source,xml,subs="attributes+"]
+----
+
+ bootable-jar
+
+ true
+
+
+
+
+ org.jboss.eap.plugins
+ eap-maven-plugin
+
+ ...
+
+
+ org.jboss.eap:wildfly-ee-galleon-pack
+
+ ...
+
+ ...
+ true
+
+
+
+
+ package
+
+
+
+
+ ...
+
+
+
+----
+endif::[]
+
+[NOTE]
+====
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
diff --git a/shared-doc/build-and-run-the-quickstart-with-provisioned-server.adoc b/shared-doc/build-and-run-the-quickstart-with-provisioned-server.adoc
index 06bb84a874..05665ea201 100644
--- a/shared-doc/build-and-run-the-quickstart-with-provisioned-server.adoc
+++ b/shared-doc/build-and-run-the-quickstart-with-provisioned-server.adoc
@@ -23,39 +23,82 @@ ifndef::extraProvisioningTestParams[:extraProvisioningTestParams: ]
Instead of using a standard {productName} server distribution, you can alternatively provision a {productName} server to deploy and run the quickstart. The functionality is provided by the WildFly Maven Plugin, and you may find its configuration in the quickstart `pom.xml`:
+ifndef::ProductRelease[]
[source,xml,subs="attributes+"]
----
-
- provisioned-server
-
- true
-
-
-
-
- org.wildfly.plugins
- wildfly-maven-plugin
-
-
- ${version.server}
-
- ...
-
-
-
-
- package
-
-
-
-
+
+ provisioned-server
+
+ true
+
+
+
+
+ org.wildfly.plugins
+ wildfly-maven-plugin
+
+
+ ${version.server}
+
+ ...
+
+
+
+
+ package
+
+
+
+
+ ...
+
+
+
+----
+endif::[]
+
+ifdef::ProductRelease[]
+[source,xml,subs="attributes+"]
+----
+
+ provisioned-server
+
+ true
+
+
+
+
+ org.jboss.eap.plugins
+ eap-maven-plugin
+
...
-
-
-
+
+
+ org.jboss.eap:wildfly-ee-galleon-pack
+
+ ...
+
+ ...
+
+
+
+
+ package
+
+
+
+
+ ...
+
+
+
----
+endif::[]
+[NOTE]
+====
When built, the provisioned {productName} server can be found in the `{deploymentTargetDir}/server` directory, and its usage is similar to a standard server distribution, with the simplification that there is never the need to specify the server configuration to be started.
+====
Follow these steps to run the quickstart using the provisioned server.
diff --git a/shared-doc/build-the-quickstart-for-cloud-platform-internal.adoc b/shared-doc/build-the-quickstart-for-cloud-platform-internal.adoc
index eb0e5dc924..5979976504 100644
--- a/shared-doc/build-the-quickstart-for-cloud-platform-internal.adoc
+++ b/shared-doc/build-the-quickstart-for-cloud-platform-internal.adoc
@@ -9,78 +9,70 @@ ifndef::ProductRelease,EAPXPRelease[]
[source,xml,subs="attributes+"]
----
-
- openshift
-
-
-
- org.wildfly.plugins
- wildfly-maven-plugin
-
-
- ${version.server}
- cloud
-
- ...
-
-
-
-
- package
-
-
-
-
- ...
-
-
-
+
+ openshift
+
+
+
+ org.wildfly.plugins
+ wildfly-maven-plugin
+
+
+ ${version.server}
+ cloud
+
+ ...
+
+
+
+
+ package
+
+
+
+
+ ...
+
+
+
----
You may note that unlike the `provisioned-server` profile it uses the cloud context which enables a configuration tuned for {cloud-platform} environment.
-
-The plugin uses https://github.com/wildfly/wildfly-glow[WildFly Glow] to discover the feature packs and layers required to run the application, and provisions a server containing those layers.
-
-If you get an error or the server is missing some functionality which cannot be auto-discovered, you can download the https://github.com/wildfly/wildfly-glow/releases[WildFly Glow CLI] and run the following command to see more information about what add-ons are available:
-[source,shell]
-----
-wildfly-glow show-add-ons
-----
endif::ProductRelease,EAPXPRelease[]
ifdef::ProductRelease,EAPXPRelease[]
[source,xml,subs="attributes+"]
----
-
- openshift
-
-
-
- org.jboss.eap.plugins
- eap-maven-plugin
-
- ...
-
-
- org.jboss.eap:wildfly-ee-galleon-pack
-
-
- org.jboss.eap.cloud:eap-cloud-galleon-pack
-
-
- ...
-
-
-
-
- package
-
-
-
-
+
+ openshift
+
+
+
+ org.jboss.eap.plugins
+ eap-maven-plugin
+
...
-
-
-
+
+
+ org.jboss.eap:wildfly-ee-galleon-pack
+
+
+ org.jboss.eap.cloud:eap-cloud-galleon-pack
+
+
+ ...
+
+
+
+
+ package
+
+
+
+
+ ...
+
+
+
----
You may note that it uses the cloud feature pack which enables a configuration tuned for the {cloud-platform} environment.
endif::[]