This is an automated email from the ASF dual-hosted git repository.

robbie pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/artemis.git


The following commit(s) were added to refs/heads/main by this push:
     new 044de42e32 ARTEMIS-5807: update various docs titles, references, 
links, images
044de42e32 is described below

commit 044de42e32849b792b628a62524cbf6013d98275
Author: Robbie Gemmell <[email protected]>
AuthorDate: Tue Dec 16 13:47:21 2025 +0000

    ARTEMIS-5807: update various docs titles, references, links, images
---
 artemis-website/pom.xml                              |   9 +++++----
 docs/hacking-guide/_maintainers.adoc                 |  12 ++++++------
 docs/hacking-guide/_tests.adoc                       |   4 ++--
 docs/hacking-guide/images/favicon.png                | Bin 25918 -> 3686 bytes
 docs/migration-guide/images/favicon.png              | Bin 25918 -> 3686 bytes
 docs/user-manual/_book.adoc                          |   4 ++--
 docs/user-manual/architecture.adoc                   |   4 ++--
 ...mbedding-activemq.adoc => embedding-artemis.adoc} |   0
 docs/user-manual/images/activemq-logo.png            | Bin 29377 -> 0 bytes
 docs/user-manual/images/artemis_text_black_small.png | Bin 0 -> 4334 bytes
 docs/user-manual/images/artemis_text_white_small.png | Bin 0 -> 4778 bytes
 docs/user-manual/images/favicon.png                  | Bin 25918 -> 3686 bytes
 docs/user-manual/index.adoc                          |   6 +++---
 13 files changed, 20 insertions(+), 19 deletions(-)

diff --git a/artemis-website/pom.xml b/artemis-website/pom.xml
index abd4c260fc..62c6086638 100644
--- a/artemis-website/pom.xml
+++ b/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>
diff --git a/docs/hacking-guide/_maintainers.adoc 
b/docs/hacking-guide/_maintainers.adoc
index 03bb9c1f2c..02437e1fdd 100644
--- a/docs/hacking-guide/_maintainers.adoc
+++ b/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
 ----
diff --git a/docs/hacking-guide/_tests.adoc b/docs/hacking-guide/_tests.adoc
index 483280050b..880ddb8ead 100644
--- a/docs/hacking-guide/_tests.adoc
+++ b/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.
\ No newline at end of file
+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.
diff --git a/docs/hacking-guide/images/favicon.png 
b/docs/hacking-guide/images/favicon.png
index 21367c2372..8702673222 100644
Binary files a/docs/hacking-guide/images/favicon.png and 
b/docs/hacking-guide/images/favicon.png differ
diff --git a/docs/migration-guide/images/favicon.png 
b/docs/migration-guide/images/favicon.png
index 21367c2372..8702673222 100644
Binary files a/docs/migration-guide/images/favicon.png and 
b/docs/migration-guide/images/favicon.png differ
diff --git a/docs/user-manual/_book.adoc b/docs/user-manual/_book.adoc
index 57c5513146..d32db5faa8 100644
--- a/docs/user-manual/_book.adoc
+++ b/docs/user-manual/_book.adoc
@@ -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]
diff --git a/docs/user-manual/architecture.adoc 
b/docs/user-manual/architecture.adoc
index 25a2f2822d..69c99a3fbc 100644
--- a/docs/user-manual/architecture.adoc
+++ b/docs/user-manual/architecture.adoc
@@ -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.
\ No newline at end of file
+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.
diff --git a/docs/user-manual/embedding-activemq.adoc 
b/docs/user-manual/embedding-artemis.adoc
similarity index 100%
rename from docs/user-manual/embedding-activemq.adoc
rename to docs/user-manual/embedding-artemis.adoc
diff --git a/docs/user-manual/images/activemq-logo.png 
b/docs/user-manual/images/activemq-logo.png
deleted file mode 100644
index 76b344d65c..0000000000
Binary files a/docs/user-manual/images/activemq-logo.png and /dev/null differ
diff --git a/docs/user-manual/images/artemis_text_black_small.png 
b/docs/user-manual/images/artemis_text_black_small.png
new file mode 100644
index 0000000000..8c1e901144
Binary files /dev/null and 
b/docs/user-manual/images/artemis_text_black_small.png differ
diff --git a/docs/user-manual/images/artemis_text_white_small.png 
b/docs/user-manual/images/artemis_text_white_small.png
new file mode 100644
index 0000000000..8b74d4b1a0
Binary files /dev/null and 
b/docs/user-manual/images/artemis_text_white_small.png differ
diff --git a/docs/user-manual/images/favicon.png 
b/docs/user-manual/images/favicon.png
index 21367c2372..8702673222 100644
Binary files a/docs/user-manual/images/favicon.png and 
b/docs/user-manual/images/favicon.png differ
diff --git a/docs/user-manual/index.adoc b/docs/user-manual/index.adoc
index dee1ebd773..3eca9fb79a 100644
--- a/docs/user-manual/index.adoc
+++ b/docs/user-manual/index.adoc
@@ -6,7 +6,7 @@ It *links* to all chapters following the same basic pattern as 
_book.adoc. These
 :idseparator: -
 :docinfo: shared
 
-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}*
@@ -138,7 +138,7 @@ image::images/activemq-logo.png[align="center"]
 * xref:graceful-shutdown.adoc#graceful-server-shutdown[Graceful Server 
Shutdown]
 * xref:web-server.adoc#embedded-web-server[Configuring & Managing the Embedded 
Web Server]
 * xref:logging.adoc#logging[Logging]
-* xref:embedding-activemq.adoc#embedding-{project-name-full-url}[Embedding 
{project-name-full}]
+* xref:embedding-artemis.adoc#embedding-{project-name-full-url}[Embedding 
{project-name-full}]
 * xref:karaf.adoc#apache-karaf-integration[Apache Karaf Integration]
 * xref:tomcat.adoc#apache-tomcat-support[Apache Tomcat Support]
 * xref:cdi-integration.adoc#cdi-integration[CDI Integration]
@@ -148,4 +148,4 @@ image::images/activemq-logo.png[align="center"]
 * xref:resource-adapter.adoc#jca-resource-adapter[JCA Resource Adapter]
 * xref:configuration-index.adoc#configuration-reference[Configuration Index]
 * xref:examples.adoc#examples[Examples]
-* xref:notice.adoc#legal-notice[Legal Notice]
\ No newline at end of file
+* xref:notice.adoc#legal-notice[Legal Notice]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to