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 8d3b879be9 ARTEMIS-5807: Update various references to repositories and 
websites
8d3b879be9 is described below

commit 8d3b879be9853a7c670388bc316edc02067539a9
Author: Robbie Gemmell <[email protected]>
AuthorDate: Wed Dec 10 12:19:35 2025 +0000

    ARTEMIS-5807: Update various references to repositories and websites
    
    Helps align with various changes made separately on the new artemis site
---
 .../activemq/artemis/core/config/Configuration.java  |  2 +-
 docs/hacking-guide/_building.adoc                    |  2 +-
 docs/hacking-guide/_code.adoc                        | 20 ++++++++++----------
 docs/hacking-guide/_maintainers.adoc                 |  6 +++---
 docs/hacking-guide/_tests.adoc                       | 12 ++++++------
 docs/user-manual/broker-plugins.adoc                 |  2 +-
 docs/user-manual/data-retention.adoc                 |  2 +-
 docs/user-manual/docinfo.html                        |  6 +++---
 docs/user-manual/docker.adoc                         |  2 +-
 docs/user-manual/examples.adoc                       |  4 ++--
 docs/user-manual/project-info.adoc                   |  8 ++++----
 docs/user-manual/resource-adapter.adoc               | 10 +++++-----
 docs/user-manual/tomcat.adoc                         |  2 +-
 docs/user-manual/using-server.adoc                   |  2 +-
 docs/user-manual/versions.adoc                       | 14 +++++++-------
 15 files changed, 47 insertions(+), 47 deletions(-)

diff --git 
a/artemis-server/src/main/java/org/apache/activemq/artemis/core/config/Configuration.java
 
b/artemis-server/src/main/java/org/apache/activemq/artemis/core/config/Configuration.java
index 1effd74b11..d3554feabb 100644
--- 
a/artemis-server/src/main/java/org/apache/activemq/artemis/core/config/Configuration.java
+++ 
b/artemis-server/src/main/java/org/apache/activemq/artemis/core/config/Configuration.java
@@ -391,7 +391,7 @@ public interface Configuration {
     * @return this
     * @throws Exception in case of Parsing errors on the URI
     * @see <a
-    * 
href="https://github.com/apache/activemq-artemis/blob/main/docs/user-manual/en/configuring-transports.md";>Configuring
+    * 
href="https://github.com/apache/artemis/blob/main/docs/user-manual/configuring-transports.adoc";>Configuring
     * the Transport</a>
     */
    Configuration addAcceptorConfiguration(String name, String uri) throws 
Exception;
diff --git a/docs/hacking-guide/_building.adoc 
b/docs/hacking-guide/_building.adoc
index f086c0f769..54608dadf2 100644
--- a/docs/hacking-guide/_building.adoc
+++ b/docs/hacking-guide/_building.adoc
@@ -72,7 +72,7 @@ It needs to be built prior to running `mvn install` to ensure 
that the ASYNCIO j
 Don't worry if you don't want to use ASYNCIO or your system does not support 
libaio.
 The broker will check at runtime to see if the required libraries and system 
dependencies are available and, if not, it will default to using NIO.
 
-To build the ASYNCIO native libraries, please follow 
link:https://github.com/apache/activemq-artemis-native[these instructions].
+To build the ASYNCIO native libraries, please follow 
link:https://github.com/apache/artemis-native[these instructions].
 
 == Open Web Application Security Project (OWASP) Report
 
diff --git a/docs/hacking-guide/_code.adoc b/docs/hacking-guide/_code.adoc
index d64ec692b3..bab365c8ff 100644
--- a/docs/hacking-guide/_code.adoc
+++ b/docs/hacking-guide/_code.adoc
@@ -1,9 +1,9 @@
 = Working with the Code
 
-While the canonical git repository is hosted on Apache hardware at 
https://gitbox.apache.org/repos/asf/activemq-artemis.git contributors are 
encouraged (but not required) to use a mirror on GitHub for collaboration and 
pull-request review functionality.
+While the canonical git repository is hosted on Apache hardware at 
https://gitbox.apache.org/repos/asf/artemis.git contributors are encouraged 
(but not required) to use a mirror on GitHub for collaboration and pull-request 
review functionality.
 Follow the steps below to get set up with GitHub, etc.
 
-If you do not wish to use GitHub for whatever reason you can follow the 
overall process outlined in the "Typical development cycle" section below but 
instead attach https://git-scm.com/docs/git-format-patch[a patch file] to the 
related JIRA or an email to the 
http://activemq.apache.org/mailing-lists.html[dev list].
+If you do not wish to use GitHub for whatever reason you can follow the 
overall process outlined in the "Typical development cycle" section below but 
instead attach https://git-scm.com/docs/git-format-patch[a patch file] to the 
related JIRA or an email to the https://artemis.apache.org/contact[dev list].
 
 == Initial Steps
 
@@ -11,16 +11,16 @@ If you do not wish to use GitHub for whatever reason you 
can follow the overall
 +
 https://github.com
 
-. Fork the apache-artemis repository into your account
+. Fork the artemis repository into your account
 +
-https://github.com/apache/activemq-artemis
+https://github.com/apache/artemis
 
 . Clone your newly forked copy onto your local workspace:
 +
 [,sh]
 ----
-$ git clone [email protected]:<your-user-name>/activemq-artemis.git
-Cloning into 'activemq-artemis'...
+$ git clone [email protected]:<your-user-name>/artemis.git
+Cloning into 'artemis'...
 remote: Counting objects: 63800, done.
 remote: Compressing objects: 100% (722/722), done.
 remote: Total 63800 (delta 149), reused 0 (delta 0), pack-reused 62748
@@ -28,13 +28,13 @@ Receiving objects: 100% (63800/63800), 18.28 MiB | 3.16 
MiB/s, done.
 Resolving deltas: 100% (28800/28800), done.
 Checking connectivity... done.
 
-$ cd activemq-artemis
+$ cd artemis
 ----
 . Add a remote reference to `upstream` for pulling future updates
 +
 [,sh]
 ----
-$ git remote add upstream https://github.com/apache/activemq-artemis
+$ git remote add upstream https://github.com/apache/artemis
 ----
 . Build with Maven
 +
@@ -115,7 +115,7 @@ $ git push origin my_cool_feature
 +
 Note that git push references the branch you are pushing and defaults to 
`main`, not your working branch.
 
-. https://activemq.apache.org/contact[Discuss your planned changes] (if you 
want feedback)
+. https://artemis.apache.org/contact[Discuss your planned changes] (if you 
want feedback)
 . Once you're finished coding your feature/fix then rebase your branch against 
the latest main (applies your patches  on top of main)
 +
 [,console]
@@ -173,7 +173,7 @@ Delta compression using up to 4 threads.
 Compressing objects: 100% (44/44), done.
 Writing objects: 100% (100/100), 10.67 KiB, done.
 Total 100 (delta 47), reused 100 (delta 47)
-To [email protected]:<your-user-name>/apache-artemis.git
+To [email protected]:<your-user-name>/artemis.git
 3382570..1fa25df  main -> main
 ----
 +
diff --git a/docs/hacking-guide/_maintainers.adoc 
b/docs/hacking-guide/_maintainers.adoc
index faa913dae7..03bb9c1f2c 100644
--- a/docs/hacking-guide/_maintainers.adoc
+++ b/docs/hacking-guide/_maintainers.adoc
@@ -37,14 +37,14 @@ Aside from the traditional `origin` and `upstream` 
repositories committers will
 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
-* `upstream` : https://github.com/apache/activemq-artemis
+* `upstream` : https://github.com/apache/artemis
 
 . Add the canonical Apache repository as a remote.
 Here we call it `apache`.
 +
 [,console]
 ----
-$ git remote add apache 
https://gitbox.apache.org/repos/asf/activemq-artemis.git
+$ git remote add apache https://gitbox.apache.org/repos/asf/artemis.git
 ----
 
 . Add the following section to your `<artemis-repo>/.git/config` statement to 
fetch all pull requests sent to the GitHub mirror.
@@ -146,7 +146,7 @@ $ pwd
 $ ./scripts/merge-PR.sh 175 ARTEMIS-229 address on Security Interface
 ----
 +
-The previous example was taken from a real case that generated this 
https://github.com/apache/activemq-artemis/commit/e85bb3ca4a75b0f1dfbe717ff90b34309e2de794[merge
 commit on #175].
+The previous example was taken from a real case that generated this 
https://github.com/apache/artemis/commit/e85bb3ca4a75b0f1dfbe717ff90b34309e2de794[merge
 commit on #175].
 
 * After this you can push to the canonical Apache repo.
 +
diff --git a/docs/hacking-guide/_tests.adoc b/docs/hacking-guide/_tests.adoc
index f5ff3d63cb..483280050b 100644
--- a/docs/hacking-guide/_tests.adoc
+++ b/docs/hacking-guide/_tests.adoc
@@ -26,22 +26,22 @@ Even complex test-cases involving multiple clustered 
brokers are relatively easy
 Almost every test in the  test-suite follows this pattern - configure broker, 
start broker, test functionality, stop broker.
 
 The test-suite uses JUnit to manage test execution and life-cycle.
-Most tests extend 
https://github.com/apache/activemq-artemis/blob/main/artemis-server/src/test/java/org/apache/activemq/artemis/tests/util/ActiveMQTestBase.java[`org.apache.activemq.artemis.tests.util.ActiveMQTestBase`]
 which contains JUnit setup and tear-down methods as well as a wealth of 
utility functions to configure, start, manage, and stop brokers as well as 
perform other common tasks.
+Most tests extend 
https://github.com/apache/artemis/blob/main/artemis-server/src/test/java/org/apache/activemq/artemis/tests/util/ActiveMQTestBase.java[`org.apache.activemq.artemis.tests.util.ActiveMQTestBase`]
 which contains JUnit setup and tear-down methods as well as a wealth of 
utility functions to configure, start, manage, and stop brokers as well as 
perform other common tasks.
 
-Check out 
https://github.com/apache/activemq-artemis/blob/main/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java[`org.apache.activemq.artemis.tests.integration.SimpleTest`].
+Check out 
https://github.com/apache/artemis/blob/main/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java[`org.apache.activemq.artemis.tests.integration.SimpleTest`].
 It's a very simple test-case that extends 
`org.apache.activemq.artemis.tests.util.ActiveMQTestBase` and uses its methods 
to configure a server, run a test, and then `super.tearDown()` cleans it up 
once the test completes.
 The test-case  includes comments to explain everything.
 As the name implies, this is a simple test-case that demonstrates the most 
basic functionality of the test-suite.
 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/activemq-artemis/blob/main/artemis-server/src/test/java/org/apache/activemq/artemis/tests/util/SingleServerTestBase.java[`org.apache.activemq.artemis.tests.util.SingleServerTestBase`].
+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/activemq-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
 
 The broker has a web console based on https://github.com/hawtio/hawtio[hawtio] 
and the `smoke-tests` are used to test it.
-For instance, the 
https://github.com/apache/activemq-artemis/blob/main/tests/smoke-tests/src/test/java/org/apache/activemq/artemis/tests/smoke/console/ConsoleTest.java[ConsoleTest]
 checks the web console using the 
https://github.com/SeleniumHQ/selenium[selenium framework].
+For instance, the 
https://github.com/apache/artemis/blob/main/tests/smoke-tests/src/test/java/org/apache/activemq/artemis/tests/smoke/console/ConsoleTest.java[ConsoleTest]
 checks the web console using the 
https://github.com/SeleniumHQ/selenium[selenium framework].
 The tests can be executed on the Chrome and Firefox browsers by using a remote 
server, local browsers or 
https://www.testcontainers.org/modules/webdriver_containers[testcontainers].
 To configure the browsers on which execute the tests set the 
`webdriver.browsers` property with the comma-separated list of the browsers, 
i.e. `-Dwebdriver.browsers=chrome,firefox`.
 To use a remote server set the `webdriver.remote.server` property with the URL 
of the server, ie -Dwebdriver.remote.server=http://localhost:4444/wd/hub To use 
your local Google Chrome browser download the 
https://chromedriver.chromium.org/[WebDriver for Chrome] and set the 
`webdriver.chrome.driver` property with the WebDriver path, ie 
`-Dwebdriver.chrome.driver=/home/artemis/chromedriver_linux64/chromedriver`.
@@ -79,7 +79,7 @@ An important task for any test-case is to clean up all the 
resources it creates
 This includes the server instance itself and any resources created to connect 
to it (e.g. instances of `ServerLocator`, `ClientSessionFactory`, 
`ClientSession`, etc.).
 This task is typically completed in the test's `tearDown()` method.
 However, `ActiveMQTestBase`  (and other classes which extend it) simplifies 
this process.
-As 
https://github.com/apache/activemq-artemis/blob/main/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java[`org.apache.activemq.artemis.tests.integration.SimpleTest`]
 demonstrates, there are several methods you can use when creating your test 
which will ensure proper clean up _automatically_ when the test is torn down.
+As 
https://github.com/apache/artemis/blob/main/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/SimpleTest.java[`org.apache.activemq.artemis.tests.integration.SimpleTest`]
 demonstrates, there are several methods you can use when creating your test 
which will ensure proper clean up _automatically_ when the test is torn down.
 These include:
 
 * All the overloaded 
`org.apache.activemq.artemis.tests.util.ActiveMQTestBase.createServer(..)` 
methods.
diff --git a/docs/user-manual/broker-plugins.adoc 
b/docs/user-manual/broker-plugins.adoc
index fc89b946f9..3345b7032c 100644
--- a/docs/user-manual/broker-plugins.adoc
+++ b/docs/user-manual/broker-plugins.adoc
@@ -9,7 +9,7 @@ Multiple plugins can be registered at the same time, and they 
will be chained to
 Creating a plugin is very simple.
 It requires:
 
-* Implementing the 
https://github.com/apache/activemq-artemis/blob/main/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/plugin/ActiveMQServerPlugin.java[`ActiveMQServerPlugin`]
 interface
+* Implementing the 
https://github.com/apache/artemis/blob/main/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/plugin/ActiveMQServerPlugin.java[`ActiveMQServerPlugin`]
 interface
 * Making sure the plugin is 
xref:using-server.adoc#adding-runtime-dependencies[on the classpath]
 * Registering it with the broker either via <<registering-a-plugin,xml>> or 
<<registering-a-plugin-programmatically,programmatically>>.
 
diff --git a/docs/user-manual/data-retention.adoc 
b/docs/user-manual/data-retention.adoc
index 15f6ef5894..a0d0cfe714 100644
--- a/docs/user-manual/data-retention.adoc
+++ b/docs/user-manual/data-retention.adoc
@@ -41,7 +41,7 @@ Non persistent messages are never stored anywhere in the 
broker. If you intend t
 
 == Recovering data from retention
 
-To recover data from the retention folder, you can use the method 
link:https://activemq.apache.org/components/artemis/documentation/javadocs/javadoc-latest/org/apache/activemq/artemis/api/core/management/ActiveMQServerControl.html#replay(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String)[replay]
 on the management console:
+To recover data from the retention folder, you can use the method 
link:https://artemis.apache.org/components/artemis/documentation/javadocs/javadoc-latest/org/apache/activemq/artemis/api/core/management/ActiveMQServerControl.html#replay(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String)[replay]
 on the management console:
 
 image::images/replay-method.png[align="center"]
 
diff --git a/docs/user-manual/docinfo.html b/docs/user-manual/docinfo.html
index 4e057c19d1..3eae382d81 100644
--- a/docs/user-manual/docinfo.html
+++ b/docs/user-manual/docinfo.html
@@ -1,7 +1,7 @@
 <script>
     document.addEventListener("DOMContentLoaded", function() {
         const pathSegments = window.location.pathname.split('/');
-        if (window.location.hostname == "activemq.apache.org" && 
pathSegments[pathSegments.length - 2] != "latest") {
+        if (window.location.hostname == "artemis.apache.org" && 
pathSegments[pathSegments.length - 2] != "latest") {
             var message = document.createElement("div");
             message.style.margin = "20px";
             message.style.textAlign = "center";
@@ -9,11 +9,11 @@
             message.textContent = "Please be aware that this documentation is 
out of date. ";
 
             var link = document.createElement("a");
-            link.href = "../latest";
+            link.href = "../../latest";
             link.textContent = "Here is the latest documentation.";
             message.appendChild(link);
 
             document.body.insertBefore(message, document.body.firstChild);
         }
     });
-</script>
\ No newline at end of file
+</script>
diff --git a/docs/user-manual/docker.adoc b/docs/user-manual/docker.adoc
index cdcf21606d..b80295ae33 100644
--- a/docs/user-manual/docker.adoc
+++ b/docs/user-manual/docker.adoc
@@ -40,7 +40,7 @@ Stop the container using:
 $ docker stop mycontainer
 ----
 
-The official Docker images are built using 
https://github.com/apache/activemq-artemis/tree/main/artemis-docker[these 
scripts] which you can also use to build your own images.
+The official Docker images are built using 
https://github.com/apache/artemis/tree/main/artemis-docker[these scripts] which 
you can also use to build your own images.
 Read on for more details.
 
 == Build your own Image
diff --git a/docs/user-manual/examples.adoc b/docs/user-manual/examples.adoc
index 76a5efa68e..81973b34d3 100644
--- a/docs/user-manual/examples.adoc
+++ b/docs/user-manual/examples.adoc
@@ -3,7 +3,7 @@
 :idseparator: -
 :docinfo: shared
 
-https://github.com/apache/activemq-artemis-examples[The Examples repository^] 
contains over 90 examples demonstrating many of the client and broker features.
+https://github.com/apache/artemis-examples[The Examples repository^] contains 
over 90 examples demonstrating many of the client and broker features.
 
 The individual examples are available under the `examples` directory, and are 
grouped within the following sub tree:
 
@@ -165,7 +165,7 @@ server-out:Server stopped!
 [INFO] ------------------------------------------------------------------------
 ----
 
-This list includes a preview of some examples in the 
https://github.com/apache/activemq-artemis-examples[Examples Repository^].
+This list includes a preview of some examples in the 
https://github.com/apache/artemis-examples[Examples Repository^].
 See the repository for more.
 
 == Application-Layer Failover
diff --git a/docs/user-manual/project-info.adoc 
b/docs/user-manual/project-info.adoc
index 19248bdda7..5cfc5fd100 100644
--- a/docs/user-manual/project-info.adoc
+++ b/docs/user-manual/project-info.adoc
@@ -6,7 +6,7 @@
 * {project-name-full} is an open source project to build a multi-protocol, 
embeddable, very high performance, clustered, asynchronous messaging system.
 * {project-name-full} is an example of Message Oriented Middleware (MoM).
 For a description of MoMs and other messaging concepts, please see the 
xref:messaging-concepts.adoc#messaging-concepts[Messaging Concepts].
-* If you have any questions related to the use or development of 
{project-name-full} please use one of our 
https://activemq.apache.org/contact[mailing lists].
-* *Official project page*: https://activemq.apache.org/components/artemis/.
-* *Download*: https://activemq.apache.org/components/artemis/download/
-* *Git repository*: 
https://github.com/apache/activemq-artemis[https://github.com/apache/activemq-artemis^]
+* If you have any questions related to the use or development of 
{project-name-full} please use one of our 
https://artemis.apache.org/contact[mailing lists].
+* *Official project page*: https://artemis.apache.org
+* *Download*: https://artemis.apache.org/components/artemis/download/
+* *Git repository*: 
https://github.com/apache/artemis[https://github.com/apache/artemis^]
diff --git a/docs/user-manual/resource-adapter.adoc 
b/docs/user-manual/resource-adapter.adoc
index d550eaae7c..7a8b9e2924 100644
--- a/docs/user-manual/resource-adapter.adoc
+++ b/docs/user-manual/resource-adapter.adoc
@@ -64,7 +64,7 @@ First the config to send messages to a destination 
(outbound), and second the co
 Each can be configured separately or both can use the ResourceAdapter settings.
 
 Here are a few options listed.
-If you want an overview of all configuration options, consider 
https://github.com/apache/activemq-artemis/blob/{{ config.version 
}}/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/ConnectionFactoryProperties.java[ConnectionFactoryProperties]
 as a base and additionally the specific classes for your object.
+If you want an overview of all configuration options, consider 
https://github.com/apache/artemis/blob/{{ config.version 
}}/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/ConnectionFactoryProperties.java[ConnectionFactoryProperties]
 as a base and additionally the specific classes for your object.
 
 Consider also the `rar.xml` file for options and explanations in your 
`artemis.rar`.
 There you can set the default options for your ResourceAdapter.
@@ -73,7 +73,7 @@ With the configuration of the ConnectionFactory or the 
ActivationSpec, you can o
 
 === ResourceAdapter
 
-Config options https://github.com/apache/activemq-artemis/blob/{{ 
config.version 
}}/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/ActiveMQRAProperties.java[ActiveMQRAProperties]
+Config options https://github.com/apache/artemis/blob/{{ config.version 
}}/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/ActiveMQRAProperties.java[ActiveMQRAProperties]
 
 connectionParameters::
 key value pairs, like host=localhost;port=61616,host=anotherHost;port=61617
@@ -89,9 +89,9 @@ clientID
 
 === ConnectionFactory
 
-Config options for the outbound `ManagedConnectionFactory`: 
https://github.com/apache/activemq-artemis/blob/{{ config.version 
}}/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/ActiveMQRAMCFProperties.java[ActiveMQRAMCFProperties]
 The connection for the `ManagedConnectionFactory` is specified by the RA.
+Config options for the outbound `ManagedConnectionFactory`: 
https://github.com/apache/artemis/blob/{{ config.version 
}}/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/ActiveMQRAMCFProperties.java[ActiveMQRAMCFProperties]
 The connection for the `ManagedConnectionFactory` is specified by the RA.
 
-Config options for the inbound `ConnectionFactory` 
https://github.com/apache/activemq-artemis/blob/{{ config.version 
}}/artemis-jms-client/src/main/java/org/apache/activemq/artemis/jms/client/ActiveMQConnectionFactory.java[ActiveMQConnectionFactory]
+Config options for the inbound `ConnectionFactory` 
https://github.com/apache/artemis/blob/{{ config.version 
}}/artemis-jms-client/src/main/java/org/apache/activemq/artemis/jms/client/ActiveMQConnectionFactory.java[ActiveMQConnectionFactory]
 
 brokerUrl::
 url to broker
@@ -105,7 +105,7 @@ You can't configure any properties.
 
 === ActivationSpec
 
-Config options https://github.com/apache/activemq-artemis/blob/{{ 
config.version 
}}/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/inflow/ActiveMQActivationSpec.java[ActiveMQActivationSpec]
+Config options https://github.com/apache/artemis/blob/{{ config.version 
}}/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/inflow/ActiveMQActivationSpec.java[ActiveMQActivationSpec]
 
 In the activation spec you can configure all the things you need to get 
messages consumed.
 
diff --git a/docs/user-manual/tomcat.adoc b/docs/user-manual/tomcat.adoc
index b44824ced6..fd249255c2 100644
--- a/docs/user-manual/tomcat.adoc
+++ b/docs/user-manual/tomcat.adoc
@@ -8,7 +8,7 @@
 A {project-name-short} client can be configured in the `context.xml` of the 
Tomcat container.
 
 This is very similar to the way this is done in ActiveMQ so anyone migrating 
should find this familiar.
-Please note, the connection url and properties are different please see 
https://activemq.apache.org/artemis/migration/[Migration Documentation]
+Please note, the connection url and properties are different please see 
https://artemis.apache.org/components/artemis/migration-documentation/[Migration
 Documentation]
 
 === Example of Connection Factory
 
diff --git a/docs/user-manual/using-server.adoc 
b/docs/user-manual/using-server.adoc
index 0c9b81cf99..5f282990c0 100644
--- a/docs/user-manual/using-server.adoc
+++ b/docs/user-manual/using-server.adoc
@@ -11,7 +11,7 @@ This document will refer to the full path of the directory 
where the ActiveMQ di
 
 == Installation
 
-You can get the latest release from the 
https://activemq.apache.org/components/artemis/download/[Download] page.
+You can get the latest release from the 
https://artemis.apache.org/components/artemis/download/[Download] page.
 
 The following highlights some important folders on the distribution:
 
diff --git a/docs/user-manual/versions.adoc b/docs/user-manual/versions.adoc
index 58d8aa7638..e6f73eb9b3 100644
--- a/docs/user-manual/versions.adoc
+++ b/docs/user-manual/versions.adoc
@@ -105,7 +105,7 @@ 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&versio
 * MQTT performance improvements for:
 ** xref:mqtt.adoc#persistent-subscriptions[persisting subscriptions]
 ** matching subscription identifiers to topic filters for 5.0 clients
-* Upgrade to 
https://activemq.apache.org/components/artemis-console/download/release-notes-1.2.1[{project-name-short}
 Console 1.2.1] with lots of usability improvements
+* Upgrade to 
https://artemis.apache.org/components/artemis-console/download/release-notes-1.2.1[{project-name-short}
 Console 1.2.1] with lots of usability improvements
 * Support for XOAUTH SASL mechanism for xref:amqp-broker-connections.adoc[AMQP 
broker connections]
 * And for developers...almost 2,500 lines of code were eliminated by 
consistently using the convenience methods from Java's `java.util.Objects` 
class across the code-base (e.g. 
https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/util/Objects.html#hash(java.lang.Object...)[`hash`],
 
https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/util/Objects.html#toString(java.lang.Object)[`toString`],
 https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/util/O [...]
 
@@ -178,7 +178,7 @@ 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&versio
 
 === Upgrading from 2.39.0
 
-* Due to EOL components in Hawio 2.x used by our web console we've moved to a 
https://github.com/apache/activemq-artemis-console[new web console] based on 
Hawtio 4.
+* Due to EOL components in Hawio 2.x used by our web console we've moved to a 
https://github.com/apache/artemis-console[new web console] based on Hawtio 4.
 This move is about security just like the recent move to Java 17.
 +
 --
@@ -385,7 +385,7 @@ 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&versio
 * Mirrored Core Messages can now be sent on their native format without 
conversions
 * Mirror bug fixes and improvements
 * https://issues.apache.org/jira/browse/ARTEMIS-3474[{project-name-short} has 
now adopted] more inclusive language definitions.
-* The examples are now part of its own repository:  
https://github.com/apache/activemq-artemis-examples/
+* The examples are now part of its own repository:  
https://github.com/apache/artemis-examples/
 
 === Upgrading from 2.31.x
 
@@ -600,7 +600,7 @@ The default `<instance>/etc/log4j2.properties` file created 
has a 5 second `moni
 Alternatively, rather than using the upgrade helper command as outlined above, 
you can instead perform the update manually, following the 
xref:upgrading.adoc#general-upgrade-procedure[general upgrading procedure] plus 
the additional steps below:
 
 . The new `<instance>/etc/log4j2.properties` file should be created with Log4J 
2 configuration.
-The file used by the "artemis create" CLI command can be downloaded from: 
https://github.com/apache/activemq-artemis/blob/2.27.0/artemis-cli/src/main/resources/org/apache/activemq/artemis/cli/commands/etc/log4j2.properties[log4j2.properties]
+The file used by the "artemis create" CLI command can be downloaded from: 
https://github.com/apache/artemis/blob/2.27.0/artemis-cli/src/main/resources/org/apache/activemq/artemis/cli/commands/etc/log4j2.properties[log4j2.properties]
 . The old `<instance>/etc/logging.properties` JBoss Logging configuration file 
should be deleted.
 . Related startup script or profile cleanups are needed: a diff file 
demonstrating the changes needed since 2.26.0 is available 
link:02-27-00-scripts-profiles.diff[here] for *nix or 
link:02-27-00-scripts-profiles-windows.diff[here] for Windows.
 
@@ -619,7 +619,7 @@ If you use these libraries they can be found at Maven 
Central (e.g. https://repo
 Please refer to the xref:client-classpath.adoc#the-client-classpath[client 
class path documentation] for more information.
 . We removed the REST interface from the code-base and documentation.
 If you still require the REST interface you can access the 
https://mvnrepository.com/artifact/org.apache.activemq.rest/artemis-rest/2.25.0[latest
 version] which is still viable.
-You can still follow the steps from the 
https://activemq.apache.org/components/artemis/documentation/2.25.0/rest.html[previous
 documentation] to build and deploy the interface.
+You can still follow the steps from the previous version to build and deploy 
the interface.
 However, you should stop using it as it will not be maintained any more.
 . Due to https://issues.apache.org/jira/browse/ARTEMIS-3980[ARTEMIS-3980] the 
web content was removed from the binary distribution.
 We now redirect web requests with the root target to the administration 
console.
@@ -1147,7 +1147,7 @@ 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&versio
 * Support xref:web-server.adoc#embedded-web-server[logging HTTP access].
 * Add a CLI command to purge a queue.
 * Support user and role manipulation for PropertiesLoginModule via management 
interfaces.
-* https://github.com/apache/activemq-artemis/tree/main/artemis-docker[Docker 
images].
+* https://github.com/apache/artemis/tree/main/artemis-docker[Docker images].
 * xref:logging.adoc#configuring-broker-audit-logging[Audit logging].
 * Implementing xref:consumer-priority.adoc#consumer-priority[consumer 
priority].
 * Support xref:address-model.adoc#fully-qualified-queue-names[FQQN] for 
producers.
@@ -1158,7 +1158,7 @@ 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&versio
 * Support xref:message-grouping.adoc#closing-a-message-group[`JMSXGroupSeq` -1 
to close/reset message groups] from Classic.
 * Allow configuration of xref:management.adoc#remote-jmx-access[RMI registry 
port].
 * Support routing-type configuration on 
xref:core-bridges.adoc#configuring-core-bridges[core bridge].
-* Move artemis-native as its own project, as 
https://github.com/apache/activemq-artemis-native[activemq-artemis-native].
+* Move artemis-native as its own project, as 
https://github.com/apache/artemis-native[artemis-native].
 * Support xref:federation.adoc#federation[federated queues and addresses].
 
 


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

Reply via email to