Merge branch 'spring-projects:main' into 2814-add-opentelemetry-tags-rabbitmq-rabbittemplate

Author: vmeunier

src/reference/antora/antora.yml

@@ -25,4 +25,6 @@ asciidoc:
     micrometer-docs: 'https://docs.micrometer.io'
     micrometer-tracing-docs: '{micrometer-docs}/tracing/reference/'
     micrometer-micrometer-docs: '{micrometer-docs}/micrometer/reference/'
-    rabbitmq-stream-docs: 'https://rabbitmq.github.io/rabbitmq-stream-java-client/stable/htmlsingle'
+    rabbitmq-stream-docs: 'https://rabbitmq.github.io/rabbitmq-stream-java-client/stable/htmlsingle'
+    rabbitmq-github: 'https://github.com/rabbitmq'
+    rabbitmq-server-github: '{rabbitmq-github}/rabbitmq-server/tree/main/deps'

src/reference/antora/modules/ROOT/pages/amqp/abstractions.adoc

@@ -93,7 +93,7 @@ Starting with version 3.2, the `ConsistentHashExchange` type has been introduced
 It provided options like `x-consistent-hash` for an exchange type.
 Allows to configure `hash-header` or `hash-property` exchange definition argument.
 The respective RabbitMQ `rabbitmq_consistent_hash_exchange` plugin has to be enabled on the broker.
-More information about the purpose, logic and behavior of the Consistent Hash Exchange are in the official RabbitMQ https://github.com/rabbitmq/rabbitmq-server/tree/main/deps/rabbitmq_consistent_hash_exchange[documentation].
+More information about the purpose, logic and behavior of the Consistent Hash Exchange are in the official RabbitMQ {rabbitmq-server-github}/rabbitmq_consistent_hash_exchange[documentation].
 
 NOTE: The AMQP specification also requires that any broker provide a "`default`" direct exchange that has no name.
 All queues that are declared are bound to that default `Exchange` with their names as routing keys.

src/reference/antora/modules/ROOT/pages/amqp/connections.adoc

@@ -429,7 +429,7 @@ Starting with version 3.0, the underlying connection factory will attempt to con
 To revert to the previous behavior of attempting to connect from first to last, set the `addressShuffleMode` property to `AddressShuffleMode.NONE`.
 
 Starting with version 2.3, the `INORDER` shuffle mode was added, which means the first address is moved to the end after a connection is created.
-You may wish to use this mode with the https://github.com/rabbitmq/rabbitmq-sharding[RabbitMQ Sharding Plugin] with `CacheMode.CONNECTION` and suitable concurrency if you wish to consume from all shards on all nodes.
+You may wish to use this mode with the {rabbitmq-server-github}/rabbitmq_sharding[RabbitMQ Sharding Plugin] with `CacheMode.CONNECTION` and suitable concurrency if you wish to consume from all shards on all nodes.
 
 [source, java]
 ----

src/reference/antora/modules/ROOT/pages/amqp/containerAttributes.adoc

@@ -250,7 +250,7 @@ a|
 |[[consumeDelay]]<<consumeDelay,`consumeDelay`>> +
 (N/A)
 
-|When using the https://github.com/rabbitmq/rabbitmq-sharding[RabbitMQ Sharding Plugin] with `concurrentConsumers > 1`, there is a race condition that can prevent even distribution of the consumers across the shards.
+|When using the {rabbitmq-server-github}/rabbitmq_sharding[RabbitMQ Sharding Plugin] with `concurrentConsumers > 1`, there is a race condition that can prevent even distribution of the consumers across the shards.
 Use this property to add a small delay between consumer starts to avoid this race condition.
 You should experiment with values to determine the suitable delay for your environment.
 

src/reference/antora/modules/ROOT/pages/amqp/management-rest-api.adoc

@@ -3,7 +3,7 @@
 :page-section-summary-toc: 1
 
 When the management plugin is enabled, the RabbitMQ server exposes a REST API to monitor and configure the broker.
-A https://github.com/rabbitmq/hop[Java Binding for the API] is now provided.
+A {rabbitmq-github}/hop[Java Binding for the API] is now provided.
 The `com.rabbitmq.http.client.Client` is a standard, immediate, and, therefore, blocking API.
 It is based on the {spring-framework-docs}/web.html[Spring Web] module and its `RestTemplate` implementation.
 On the other hand, the `com.rabbitmq.http.client.ReactorNettyClient` is a reactive, non-blocking implementation based on the https://projectreactor.io/docs/netty/release/reference/docs/index.html[Reactor Netty] project.

src/reference/antora/modules/ROOT/pages/appendix/previous-whats-new/changes-in-1-3-since-1-2.adoc

@@ -70,7 +70,7 @@ See xref:amqp/broker-configuration.adoc#headers-exchange[Headers Exchange].
 
 A new `SimpleRoutingConnectionFactory` has been introduced.
 It allows configuration of `ConnectionFactories` mapping, to determine the target `ConnectionFactory` to use at runtime.
-See xref:amqp/connections.adoc#routing-connection-factory[routing-connection-factory].
+See xref:amqp/connections.adoc#routing-connection-factory[Routing Connection Factory].
 
 [[messagebuilder-and-messagepropertiesbuilder]]
 == `MessageBuilder` and `MessagePropertiesBuilder`

src/reference/antora/modules/ROOT/pages/appendix/previous-whats-new/changes-in-1-4-since-1-3.adoc

@@ -71,13 +71,13 @@ The `mandatoryExpression`, `sendConnectionFactorySelectorExpression`, and `recei
 The `mandatoryExpression` is used to evaluate a `mandatory` boolean value against each request message when a `ReturnCallback` is in use.
 See xref:amqp/template.adoc#template-confirms[Correlated Publisher Confirms and Returns].
 The `sendConnectionFactorySelectorExpression` and `receiveConnectionFactorySelectorExpression` are used when an `AbstractRoutingConnectionFactory` is provided, to determine the `lookupKey` for the target `ConnectionFactory` at runtime on each AMQP protocol interaction operation.
-See xref:amqp/connections.adoc#routing-connection-factory[routing-connection-factory].
+See xref:amqp/connections.adoc#routing-connection-factory[Routing Connection Factory].
 
 [[listeners-and-the-routing-connection-factory]]
 == Listeners and the Routing Connection Factory
 
 You can configure a `SimpleMessageListenerContainer` with a routing connection factory to enable connection selection based on the queue names.
-See xref:amqp/connections.adoc#routing-connection-factory[routing-connection-factory].
+See xref:amqp/connections.adoc#routing-connection-factory[Routing Connection Factory].
 
 [[rabbittemplate:-recoverycallback-option]]
 == `RabbitTemplate`: `RecoveryCallback` Option

src/reference/antora/modules/ROOT/pages/appendix/previous-whats-new/changes-in-2-3-since-2-2.adoc

@@ -43,7 +43,7 @@ See xref:amqp/request-reply.adoc#direct-reply-to[RabbitMQ Direct reply-to] for m
 [[listener-container-changes]]
 == Listener Container Changes
 
-A new listener container property `consumeDelay` is now available; it is helpful when using the https://github.com/rabbitmq/rabbitmq-sharding[RabbitMQ Sharding Plugin].
+A new listener container property `consumeDelay` is now available; it is helpful when using the {rabbitmq-server-github}/rabbitmq_sharding[RabbitMQ Sharding Plugin].
 
 The default `JavaLangErrorHandler` now calls `System.exit(99)`.
 To revert to the previous behavior (do nothing), add a no-op handler.

src/reference/antora/modules/ROOT/pages/stream.adoc

@@ -1,7 +1,7 @@
 [[stream-support]]
 = Using the RabbitMQ Stream Plugin
 
-Version 2.4 introduces initial support for the https://github.com/rabbitmq/rabbitmq-stream-java-client[RabbitMQ Stream Plugin Java Client] for the https://rabbitmq.com/stream.html[RabbitMQ Stream Plugin].
+Version 2.4 introduces initial support for the {rabbitmq-github}/rabbitmq-stream-java-client[RabbitMQ Stream Plugin Java Client] for the https://rabbitmq.com/stream.html[RabbitMQ Stream Plugin].
 
 * `RabbitStreamTemplate`
 * `StreamListenerContainer`