ARTEMIS-5807: update various docs titles, references, links, images

Author: gemmellr

artemis-website/pom.xml

@@ -90,7 +90,8 @@
                            <goal>jar</goal>
                         </goals>
                         <configuration>
-                           <doctitle>ActiveMQ Artemis ${project.version} API</doctitle>
+                           <windowtitle>Apache Artemis ${project.version} API</windowtitle>
+                           <doctitle>Apache Artemis ${project.version} API</doctitle>
                            <minmemory>128m</minmemory>
                            <maxmemory>512m</maxmemory>
                            <noindex>true</noindex>
@@ -381,9 +382,9 @@
 
                         <!-- Version substitution attributes -->
                         <project-version>${project.version}</project-version>
-                        <project-name-full>Apache ActiveMQ Artemis</project-name-full>
-                        <project-name-full-url>apache-activemq-artemis</project-name-full-url>
-                        <project-name-short>ActiveMQ Artemis</project-name-short>
+                        <project-name-full>Apache Artemis</project-name-full>
+                        <project-name-full-url>apache-artemis</project-name-full-url>
+                        <project-name-short>Artemis</project-name-short>
                         <log4j-version>${log4j.version}</log4j-version>
                      </attributes>
                      <logHandler>

docs/hacking-guide/_maintainers.adoc

@@ -7,10 +7,10 @@ However, the expectation here is that the developer has made a good effort to te
 
 What does it mean to be reasonably confident?
 If the developer has run the same maven commands that the pull-request builds are running they can be reasonably confident.
-Currently the https://builds.apache.org/job/ActiveMQ-Artemis-PR-Build/[PR build] runs this command:
+Currently the https://github.com/apache/artemis/blob/main/.github/workflows/build.yml[PR build] runs this command:
 [,console]
 ----
-$ mvn -Pfast-tests install
+$ mvn -Pfast-tests -Pcompatibility-tests install
 ----
 However, if the changes are significant, touches a wide area of code, or even if the developer just wants a second opinion they are encouraged to engage other members of the community to obtain an additional review prior to pushing.
 This can easily be done via a pull request on GitHub, a patch file attached to an email or JIRA, commit to a branch in the Apache git repo, etc.
@@ -36,7 +36,7 @@ This format follows the recommendation from the https://git-scm.com/book/en/v2/D
 Aside from the traditional `origin` and `upstream` repositories committers will need an additional reference for the canonical Apache git repository where they will be merging and pushing pull-requests.
 For the purposes of this document, let's assume these ref/repo associations already exist as described in the xref:code.adoc[Working with the Code] section:
 
-* `origin` : https://github.com/(your-user-name)/activemq-artemis.git
+* `origin` : https://github.com/(your-user-name)/artemis.git
 * `upstream` : https://github.com/apache/artemis
 
 . Add the canonical Apache repository as a remote.
@@ -54,7 +54,7 @@ Just be sure to edit all references to the remote repo name so it's consistent.
 [,console]
 ----
  [remote "upstream"]
-     url = [email protected]:apache/activemq-artemis.git
+     url = [email protected]:apache/artemis.git
      fetch = +refs/heads/*:refs/remotes/upstream/*
      fetch = +refs/pull/*/head:refs/remotes/upstream/pr/*
 ----
@@ -75,7 +75,7 @@ remote: Compressing objects: 100% (188/188), done.
 remote: Total 566 (delta 64), reused 17 (delta 17), pack-reused 351
 Receiving objects: 100% (566/566), 300.67 KiB | 0 bytes/s, done.
 Resolving deltas: 100% (78/78), done.
-From github.com:apache/activemq-artemis
+From github.com:apache/artemis
 * [new ref]         refs/pull/105/head -> upstream/pr/105
 ----
 . Checkout the pull request you wish to review
@@ -141,7 +141,7 @@ Example:
 [,console]
 ----
 $ pwd
-/checkouts/apache-activemq-artemis
+/checkouts/artemis
 
 $ ./scripts/merge-PR.sh 175 ARTEMIS-229 address on Security Interface
 ----

docs/hacking-guide/_tests.adoc

@@ -36,7 +36,7 @@ A simple test like this takes less than a second to run on modern hardware.
 
 Although `org.apache.activemq.artemis.tests.integration.SimpleTest` is simple it could be simpler still by extending https://github.com/apache/artemis/blob/main/artemis-server/src/test/java/org/apache/activemq/artemis/tests/util/SingleServerTestBase.java[`org.apache.activemq.artemis.tests.util.SingleServerTestBase`].
 This class does all the setup of a simple server automatically and provides the test-case with a `ServerLocator`,  `ClientSessionFactory`, and `ClientSession` instance.
-https://github.com/apache/artemis/blob/main//tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SingleServerSimpleTest.java[`org.apache.activemq.artemis.tests.integration.SingleServerSimpleTest`] is an example based on `org.apache.activemq.artemis.tests.integration.SimpleTest` but extends `org.apache.activemq.artemis.tests.util.SingleServerTestBase` which eliminates all the setup and class variables which are provided by `SingleServerTestBase` itself.
+https://github.com/apache/artemis/blob/main/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SingleServerSimpleTest.java[`org.apache.activemq.artemis.tests.integration.SingleServerSimpleTest`] is an example based on `org.apache.activemq.artemis.tests.integration.SimpleTest` but extends `org.apache.activemq.artemis.tests.util.SingleServerTestBase` which eliminates all the setup and class variables which are provided by `SingleServerTestBase` itself.
 
 == Writing Web Tests
 
@@ -102,4 +102,4 @@ In any case, `org.apache.activemq.artemis.core.config.Configuration` is a https:
 === Look at other test-cases
 
 If you need ideas on how to configure something or test something try looking through the test-suite at other test-cases which may be similar.
-This is one of the best ways to learn how the test-suite works and how you can leverage the testing infrastructure to test your particular case.
+This is one of the best ways to learn how the test-suite works and how you can leverage the testing infrastructure to test your particular case.

docs/hacking-guide/images/favicon.png

@@ -2,7 +2,7 @@
 This is used to generate the single-page PDF manual.
 It *aggregates* all chapters into a single document following the same pattern as index.adoc. These two documents should stay in sync.
 ////
-image::images/activemq-logo.png[align="center"]
+image::images/artemis_text_black_small.png[align="center"]
 
 [.text-center]
 *An in-depth manual on all aspects of {project-name-full} {project-version}*
@@ -126,7 +126,7 @@ include::send-guarantees.adoc[leveloffset=1]
 include::graceful-shutdown.adoc[leveloffset=1]
 include::web-server.adoc[leveloffset=1]
 include::logging.adoc[leveloffset=1]
-include::embedding-activemq.adoc[leveloffset=1]
+include::embedding-artemis.adoc[leveloffset=1]
 include::karaf.adoc[leveloffset=1]
 include::tomcat.adoc[leveloffset=1]
 include::cdi-integration.adoc[leveloffset=1]

docs/migration-guide/images/favicon.png

@@ -53,7 +53,7 @@ For more information on server configuration files see xref:configuration-index.
 
 The broker is designed as a set of simple POJOs so if you have an application that requires messaging functionality internally, but you don't want to expose that as an independent, standalone broker, you can directly instantiate and embed a broker in your own application.
 
-Read more about xref:embedding-activemq.adoc#embedding-{project-name-full-url}[embedding a broker].
+Read more about xref:embedding-artemis.adoc#embedding-{project-name-full-url}[embedding a broker].
 
 == Integrated with a Java/Jakarta EE application server
 
@@ -77,4 +77,4 @@ It is possible to talk to a JMS messaging system directly from an EJB, MDB or se
 Note that all communication between EJB sessions or entity beans and Message Driven beans go through the adaptor and not directly to the broker.
 
 The large arrow with the prohibited sign shows an EJB session bean talking directly to the the broker.
-This is not recommended as you'll most likely end up creating a new connection and session every time you want to interact from the EJB, which is an anti-pattern.
+This is not recommended as you'll most likely end up creating a new connection and session every time you want to interact from the EJB, which is an anti-pattern.