ARTEMIS-5807: more doc updates around new TLP

Author: gemmellr

docs/hacking-guide/_building.adoc

@@ -86,6 +86,6 @@ The output for every module will be aggregated in `./target/dependency-check-rep
 
 == Snapshot Builds
 
-Snapshot builds are available at https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-artemis/.
+Snapshot builds are available at https://repository.apache.org/content/repositories/snapshots/org/apache/artemis/apache-artemis/.
 
-These are built by https://ci-builds.apache.org/job/ActiveMQ/job/ActiveMQ-Artemis-SNAPSHOT-Deploy/[this Apache CI job].
+These are built by https://ci-builds.apache.org/job/Artemis/job/Artemis-SNAPSHOT-Deploy/[this Apache CI job].

docs/hacking-guide/_code.adoc

@@ -43,22 +43,18 @@ For example:
 +
 [,sh]
 ----
-$ mvn -Pdev install
+$ mvn -Pdev install -DskipTests
 ...
 [INFO] ------------------------------------------------------------------------
-[INFO] Reactor Summary:
+[INFO] Reactor Summary for Apache Artemis <VERSION>-SNAPSHOT:
 [INFO]
-[INFO] ActiveMQ Artemis Parent ........................... SUCCESS [2.298s]
-[INFO] ActiveMQ Artemis Commons .......................... SUCCESS [1.821s]
-[INFO] ActiveMQ Artemis Selector Implementation .......... SUCCESS [0.767s]
-[INFO] ActiveMQ Artemis Native POM ....................... SUCCESS [0.189s]
-[INFO] ActiveMQ Artemis Journal .......................... SUCCESS [0.646s]
-[INFO] ActiveMQ Artemis Core Client ...................... SUCCESS [5.969s]
-[INFO] ActiveMQ Artemis JMS Client ....................... SUCCESS [2.110s]
-[INFO] ActiveMQ Artemis Server ........................... SUCCESS [11.540s]
-...
-[INFO] ActiveMQ Artemis stress Tests ..................... SUCCESS [0.332s]
-[INFO] ActiveMQ Artemis performance Tests ................ SUCCESS [0.174s]
+[INFO] Apache Artemis ..................................... SUCCESS [  2.435 s]
+[INFO] Apache Artemis Bill of Materials ................... SUCCESS [  0.094 s]
+...etc...
+[INFO] Apache Artemis Server .............................. SUCCESS [ 11.866 s]
+...etc...
+[INFO] Apache Artemis JMS Client .......................... SUCCESS [  1.036 s]
+...etc...
 [INFO] ------------------------------------------------------------------------
 [INFO] BUILD SUCCESS
 [INFO] ------------------------------------------------------------------------
@@ -139,7 +135,7 @@ Therefore you'll want to make sure that you  either work in a branch that you do
 
 . Get your changes merged into upstream
 .. Send a GitHub pull request, by clicking the pull request link while in your repo's fork.
-.. An email will automatically be sent to the ActiveMQ developer list.
+.. An email will automatically be sent to the Artemis issues mailing list.
 .. As part of the review you may see an automated test run comment on your request.
 .. After review a maintainer will merge your PR into the canonical git repository at which point those changes will  be synced with the GitHub mirror repository (i.e. your `main`) and your PR will be closed by the `asfgit` bot.
 

docs/hacking-guide/_validating-releases.adoc

@@ -6,10 +6,10 @@ When a release is proposed a maven repository is staged.
 
 This information was extracted from https://maven.apache.org/guides/development/guide-testing-releases.html[Guide to Testing Staged Releases]
 
-For examples, the 1.1.0 release had the Maven Repository staged as https://repository.apache.org/content/repositories/orgapacheactivemq-1066.
+An example staging repository created during the release process would be: https://repository.apache.org/content/repositories/orgapacheartemis-1002.
 
-The first thing you need to do is to be able to use this release.
-The easiest way we have found is to change your maven settings at `~/.m2/settings.xml`, setting up the staged repo.
+The first thing you need to do is to be able to access this staging repository.
+The easiest way we have found is to change your maven settings at `~/.m2/settings.xml`, setting up the staging repo.
 
 [,xml]
 .~/.m2/settings.xml
@@ -18,49 +18,42 @@ The easiest way we have found is to change your maven settings at `~/.m2/setting
 <settings>
    <profiles>
       <profile>
-         <id>activemq-artemis-test</id>
+         <id>apache-artemis-staging</id>
          <repositories>
             <repository>
-               <id>artemis-test</id>
-               <name>ActiveMQ Artemis Test</name>
-               <url>https://repository.apache.org/content/repositories/orgapacheactivemq-1066</url>
+               <id>artemis-staging</id>
+               <name>Apache Artemis Staging</name>
+               <url>https://repository.apache.org/content/repositories/orgapacheartemis-1002</url>
                <layout>default</layout>
                <releases>
                   <enabled>true</enabled>
                </releases>
                <snapshots>
-                  <enabled>true</enabled>
+                  <enabled>false</enabled>
                </snapshots>
             </repository>
          </repositories>
 
          <pluginRepositories>
             <pluginRepository>
-               <id>artemis-test2</id>
-               <name>ActiveMQ Artemis Test</name>
-               <url>https://repository.apache.org/content/repositories/orgapacheactivemq-1066</url>
+               <id>artemis-staging</id>
+               <name>Apache Artemis Staging</name>
+               <url>https://repository.apache.org/content/repositories/orgapacheartemis-1002</url>
                <releases>
                   <enabled>true</enabled>
                </releases>
                <snapshots>
-                  <enabled>true</enabled>
+                  <enabled>false</enabled>
                </snapshots>
             </pluginRepository>
          </pluginRepositories>
       </profile>
    </profiles>
 
    <activeProfiles>
-      <activeProfile>activemq-artemis-test</activeProfile>
+      <activeProfile>apache-artemis-staging</activeProfile>
    </activeProfiles>
 </settings>
 ----
 
-After you configure this, all the maven objects will be available to your builds.
-
-== Using the examples
-
-The examples will create servers and use most of the maven components as real application were supposed to do.
-You can do this by running these examples after the `.m2` profile installations for the staged repository.
-
-Of course, you can use your own applications after you have staged the maven repository.
+After you configure this, the maven artifacts for the release candidate will be available to your builds.

docs/user-manual/configuring-transports.adoc

@@ -303,30 +303,30 @@ When used on an `acceptor` this is the path to the SSL key store on the server w
 When used on a `connector` this is the path to the client-side SSL key store which holds the client certificates.
 This is only relevant for a `connector` if you are using 2-way SSL (i.e. mutual authentication).
 Although this value is configured on the server, it is downloaded and used by the client.
-If the client needs to use a different path from that set on the server then it can override the server-side setting by either using the customary "javax.net.ssl.keyStore" system property or the ActiveMQ-specific "org.apache.activemq.ssl.keyStore" system property.
-The ActiveMQ-specific system property is useful if another component on the client is already making use of the standard Java system property.
+If the client needs to use a different path from that set on the server then it can override the server-side setting by either using the customary "javax.net.ssl.keyStore" system property or the Artemis-specific "org.apache.activemq.ssl.keyStore" system property.
+The Artemis-specific system property is useful if another component on the client is already making use of the standard Java system property.
 
 keyStorePassword::
 When used on an `acceptor` this is the password for the server-side keystore.
 +
 When used on a `connector` this is the password for the client-side keystore.
 This is only relevant for a `connector` if you are using 2-way SSL (i.e. mutual authentication).
 Although this value can be configured on the server, it is downloaded and used by the client.
-If the client needs to use a different password from that set on the server then it can override the server-side setting by either using the customary "javax.net.ssl.keyStorePassword" system property or the ActiveMQ-specific "org.apache.activemq.ssl.keyStorePassword" system property.
-The ActiveMQ-specific system property is useful if another component on the client is already making use of the standard Java system property.
+If the client needs to use a different password from that set on the server then it can override the server-side setting by either using the customary "javax.net.ssl.keyStorePassword" system property or the Artemis-specific "org.apache.activemq.ssl.keyStorePassword" system property.
+The Artemis-specific system property is useful if another component on the client is already making use of the standard Java system property.
 
 keyStoreType::
 The type of keystore being used.
 For example, `JKS`, `JCEKS`, `PKCS12`, `PEM` etc.
-This value can also be set via the "javax.net.ssl.keyStoreType" system property or the ActiveMQ-specific "org.apache.activemq.ssl.keyStoreType" system property.
-The ActiveMQ-specific system property is useful if another component on the  client is already making use of the standard Java system property.
+This value can also be set via the "javax.net.ssl.keyStoreType" system property or the Artemis-specific "org.apache.activemq.ssl.keyStoreType" system property.
+The Artemis-specific system property is useful if another component on the  client is already making use of the standard Java system property.
 Default is `JKS`.
 
 keyStoreProvider::
 The provider used for the keystore.
 For example, `SUN`, `SunJCE`, etc.
-This  value can also be set via the "javax.net.ssl.keyStoreProvider" system property or the ActiveMQ-specific "org.apache.activemq.ssl.keyStoreProvider" system property.
-The ActiveMQ-specific system property is useful if another component on the client is already making use of the standard Java system property.
+This  value can also be set via the "javax.net.ssl.keyStoreProvider" system property or the Artemis-specific "org.apache.activemq.ssl.keyStoreProvider" system property.
+The Artemis-specific system property is useful if another component on the client is already making use of the standard Java system property.
 Default is `null`.
 
 keyStoreAlias::
@@ -343,30 +343,30 @@ This is only relevant for an `acceptor` if you are using 2-way SSL (i.e. mutual
 +
 When used on a `connector` this is the path to the client-side SSL key store which holds the public keys of all the servers that the client trusts.
 Although this value can be configured on the server, it is downloaded and used by the client.
-If the client needs to use a different path from that set on the server then it can override the server-side setting by either using the customary "javax.net.ssl.trustStore" system property or the ActiveMQ-specific "org.apache.activemq.ssl.trustStore" system property.
-The ActiveMQ-specific system property is useful if another component on the client is already making use of the standard Java system property.
+If the client needs to use a different path from that set on the server then it can override the server-side setting by either using the customary "javax.net.ssl.trustStore" system property or the Artemis-specific "org.apache.activemq.ssl.trustStore" system property.
+The Artemis-specific system property is useful if another component on the client is already making use of the standard Java system property.
 
 trustStorePassword::
 When used on an `acceptor` this is the password for the server-side trust store.
 This is only relevant for an `acceptor` if you are using 2-way SSL (i.e. mutual authentication).
 +
 When used on a `connector` this is the password for the client-side truststore.
 Although this value can be configured on the server, it is downloaded and used by the client.
-If the client needs to use a different password from that set on the server then it can override the server-side setting by either using the customary "javax.net.ssl.trustStorePassword" system property or the ActiveMQ-specific "org.apache.activemq.ssl.trustStorePassword" system property.
-The ActiveMQ-specific system property is useful if another component on the client is already making use of the standard Java system property.
+If the client needs to use a different password from that set on the server then it can override the server-side setting by either using the customary "javax.net.ssl.trustStorePassword" system property or the Artemis-specific "org.apache.activemq.ssl.trustStorePassword" system property.
+The Artemis-specific system property is useful if another component on the client is already making use of the standard Java system property.
 
 trustStoreType::
 The type of truststore being used.
 For example, `JKS`, `JCEKS`, `PKCS12`, `PEM` etc.
-This value can also be set via the "javax.net.ssl.trustStoreType" system property or the ActiveMQ-specific "org.apache.activemq.ssl.trustStoreType" system property.
-The ActiveMQ-specific system property is useful if another component on the client is already making use of the standard Java system property.
+This value can also be set via the "javax.net.ssl.trustStoreType" system property or the Artemis-specific "org.apache.activemq.ssl.trustStoreType" system property.
+The Artemis-specific system property is useful if another component on the client is already making use of the standard Java system property.
 Default is `JKS`.
 
 trustStoreProvider::
 The provider used for the truststore.
 For example, `SUN`, `SunJCE`, etc.
-This value can also be set via the "javax.net.ssl.trustStoreProvider" system property or the ActiveMQ-specific "org.apache.activemq.ssl.trustStoreProvider" system property.
-The ActiveMQ-specific system property is useful if another component on the client is already making use of the standard Java system property.
+This value can also be set via the "javax.net.ssl.trustStoreProvider" system property or the Artemis-specific "org.apache.activemq.ssl.trustStoreProvider" system property.
+The Artemis-specific system property is useful if another component on the client is already making use of the standard Java system property.
 Default is `null`.
 
 enabledCipherSuites::
@@ -412,7 +412,7 @@ Valid values are `true` or `false`.
 Default is `false`.
 
 forceSSLParameters::
-When used on a `connector` any SSL settings that are set as parameters on the connector will be used instead of JVM system properties including both javax.net.ssl and ActiveMQ system properties to configure the SSL context for this connector.
+When used on a `connector` any SSL settings that are set as parameters on the connector will be used instead of JVM system properties including both javax.net.ssl and Artemis system properties to configure the SSL context for this connector.
 +
 Valid values are `true` or `false`.
 Default is `false`.

docs/user-manual/docker.adoc

@@ -49,7 +49,7 @@ In order to build an image you need a binary distribution.
 This can be sourced *locally* (in which case you need to build the project first) or *remotely* based on an official Apache release.
 
 === Using a Local Release
-If you want to use a local binary distribution then build it from the root of the ActiveMQ source tree, e.g.:
+If you want to use a local binary distribution then build it from the root of the Artemis source tree, e.g.:
 [,console]
 ----
 $ mvn -Prelease package -DskipTests