Make Quarkus Micrometer optional for Reactor Netty extension

Fixes apache#2442

docs/modules/ROOT/pages/reference/extensions/azure-eventhubs.adoc

@@ -38,6 +38,22 @@ Or add the coordinates to your existing project:
 
 Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
 
+== Usage
+
+=== Micrometer metrics support
+
+If you wish to enable the collection of Micrometer metrics for the Reactor Netty transports, then you should declare a dependency on `quarkus-micrometer` to ensure
+that they are available via the Quarkus metrics HTTP endpoint.
+
+[source,xml]
+----
+<dependency>
+    <groupId>io.quarkus</groupId>
+    <artifactId>quarkus-micrometer</artifactId>
+</dependency>
+----
+
+
 == SSL in native mode
 
 This extension auto-enables SSL support in native mode. Hence you do not need to add

docs/modules/ROOT/pages/reference/extensions/azure-storage-blob.adoc

@@ -38,6 +38,22 @@ Or add the coordinates to your existing project:
 
 Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
 
+== Usage
+
+=== Micrometer metrics support
+
+If you wish to enable the collection of Micrometer metrics for the Reactor Netty transports, then you should declare a dependency on `quarkus-micrometer` to ensure
+that they are available via the Quarkus metrics HTTP endpoint.
+
+[source,xml]
+----
+<dependency>
+    <groupId>io.quarkus</groupId>
+    <artifactId>quarkus-micrometer</artifactId>
+</dependency>
+----
+
+
 == SSL in native mode
 
 This extension auto-enables SSL support in native mode. Hence you do not need to add

docs/modules/ROOT/pages/reference/extensions/azure-storage-datalake.adoc

@@ -33,3 +33,19 @@ Please refer to the above link for usage and configuration details.
 ----
 
 Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
+
+== Usage
+
+=== Micrometer metrics support
+
+If you wish to enable the collection of Micrometer metrics for the Reactor Netty transports, then you should declare a dependency on `quarkus-micrometer` to ensure
+that they are available via the Quarkus metrics HTTP endpoint.
+
+[source,xml]
+----
+<dependency>
+    <groupId>io.quarkus</groupId>
+    <artifactId>quarkus-micrometer</artifactId>
+</dependency>
+----
+

docs/modules/ROOT/pages/reference/extensions/azure-storage-queue.adoc

@@ -38,6 +38,22 @@ Or add the coordinates to your existing project:
 
 Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
 
+== Usage
+
+=== Micrometer metrics support
+
+If you wish to enable the collection of Micrometer metrics for the Reactor Netty transports, then you should declare a dependency on `quarkus-micrometer` to ensure
+that they are available via the Quarkus metrics HTTP endpoint.
+
+[source,xml]
+----
+<dependency>
+    <groupId>io.quarkus</groupId>
+    <artifactId>quarkus-micrometer</artifactId>
+</dependency>
+----
+
+
 == SSL in native mode
 
 This extension auto-enables SSL support in native mode. Hence you do not need to add

extensions-jvm/azure-storage-datalake/runtime/src/main/doc/usage.adoc

@@ -0,0 +1,12 @@
+=== Micrometer metrics support
+
+If you wish to enable the collection of Micrometer metrics for the Reactor Netty transports, then you should declare a dependency on `quarkus-micrometer` to ensure
+that they are available via the Quarkus metrics HTTP endpoint.
+
+[source,xml]
+----
+<dependency>
+    <groupId>io.quarkus</groupId>
+    <artifactId>quarkus-micrometer</artifactId>
+</dependency>
+----

extensions-support/reactor-netty/deployment/pom.xml

@@ -38,10 +38,6 @@
             <groupId>io.quarkus</groupId>
             <artifactId>quarkus-netty-deployment</artifactId>
         </dependency>
-        <dependency>
-            <groupId>io.quarkus</groupId>
-            <artifactId>quarkus-micrometer-deployment</artifactId>
-        </dependency>
         <dependency>
             <groupId>org.apache.camel.quarkus</groupId>
             <artifactId>camel-quarkus-support-reactor-netty</artifactId>

extensions-support/reactor-netty/runtime/pom.xml

@@ -56,17 +56,12 @@
             <artifactId>quarkus-netty</artifactId>
         </dependency>
         <dependency>
-            <groupId>io.projectreactor.netty</groupId>
-            <artifactId>reactor-netty</artifactId>
+            <groupId>io.micrometer</groupId>
+            <artifactId>micrometer-core</artifactId>
         </dependency>
         <dependency>
-            <groupId>io.quarkus</groupId>
-            <artifactId>quarkus-micrometer</artifactId>
-        </dependency>
-        <dependency>
-            <groupId>org.graalvm.nativeimage</groupId>
-            <artifactId>svm</artifactId>
-            <scope>provided</scope>
+            <groupId>io.projectreactor.netty</groupId>
+            <artifactId>reactor-netty</artifactId>
         </dependency>
     </dependencies>
 

extensions/azure-eventhubs/runtime/src/main/doc/usage.adoc

@@ -0,0 +1,12 @@
+=== Micrometer metrics support
+
+If you wish to enable the collection of Micrometer metrics for the Reactor Netty transports, then you should declare a dependency on `quarkus-micrometer` to ensure
+that they are available via the Quarkus metrics HTTP endpoint.
+
+[source,xml]
+----
+<dependency>
+    <groupId>io.quarkus</groupId>
+    <artifactId>quarkus-micrometer</artifactId>
+</dependency>
+----

extensions/azure-storage-blob/runtime/src/main/doc/usage.adoc

@@ -0,0 +1,12 @@
+=== Micrometer metrics support
+
+If you wish to enable the collection of Micrometer metrics for the Reactor Netty transports, then you should declare a dependency on `quarkus-micrometer` to ensure
+that they are available via the Quarkus metrics HTTP endpoint.
+
+[source,xml]
+----
+<dependency>
+    <groupId>io.quarkus</groupId>
+    <artifactId>quarkus-micrometer</artifactId>
+</dependency>
+----

extensions/azure-storage-queue/runtime/src/main/doc/usage.adoc

@@ -0,0 +1,12 @@
+=== Micrometer metrics support
+
+If you wish to enable the collection of Micrometer metrics for the Reactor Netty transports, then you should declare a dependency on `quarkus-micrometer` to ensure
+that they are available via the Quarkus metrics HTTP endpoint.
+
+[source,xml]
+----
+<dependency>
+    <groupId>io.quarkus</groupId>
+    <artifactId>quarkus-micrometer</artifactId>
+</dependency>
+----