diff --git a/002-quarkus-all-extensions/pom.xml b/002-quarkus-all-extensions/pom.xml
index 4c0b3a25..5701fe10 100644
--- a/002-quarkus-all-extensions/pom.xml
+++ b/002-quarkus-all-extensions/pom.xml
@@ -78,7 +78,7 @@
io.quarkus
- quarkus-smallrye-reactive-messaging-kafka
+ quarkus-messaging-kafka
io.quarkus
@@ -154,7 +154,7 @@
io.quarkus
- quarkus-smallrye-reactive-messaging-amqp
+ quarkus-messaging-amqp
io.quarkus
@@ -198,7 +198,7 @@
io.quarkus
- quarkus-smallrye-reactive-messaging
+ quarkus-messaging
io.quarkus
@@ -367,7 +367,7 @@
io.quarkus
- quarkus-smallrye-reactive-messaging-mqtt
+ quarkus-messaging-mqtt
diff --git a/003-quarkus-many-extensions/pom.xml b/003-quarkus-many-extensions/pom.xml
index c5085c25..a74c7ddd 100644
--- a/003-quarkus-many-extensions/pom.xml
+++ b/003-quarkus-many-extensions/pom.xml
@@ -45,7 +45,7 @@
io.quarkus
- quarkus-smallrye-reactive-messaging-amqp
+ quarkus-messaging-amqp
io.quarkus
@@ -119,7 +119,7 @@
io.quarkus
- quarkus-smallrye-reactive-messaging-kafka
+ quarkus-messaging-kafka
io.quarkus
@@ -135,7 +135,7 @@
io.quarkus
- quarkus-smallrye-reactive-messaging
+ quarkus-messaging
io.quarkus
diff --git a/301-quarkus-vertx-kafka/README.md b/301-quarkus-vertx-kafka/README.md
index a92589cd..e25aa7a1 100644
--- a/301-quarkus-vertx-kafka/README.md
+++ b/301-quarkus-vertx-kafka/README.md
@@ -34,8 +34,8 @@ Vert.x Kafka exploratory test.
* Test profiles (Strimzi/Confluent)
**Brief description:** A [verticle][1] deployer launch a [periodic verticle][2] that is going to be producing random Stock-market values and push it to a Kafka Topic (`stock-price`).
-A reactive kafka consumer (`quarkus-smallrye-reactive-messaging-kafka`) will be subscribed to this topic and will change the status of the incoming events from `pending` to `completed`, and moving these records to `end-stock-price` topic.
-Note that there is another verticle `KStockPriceConsumer` launched by our verticle deployer, that does nothing. The reason is because `quarkus-smallrye-reactive-messaging-kafka` is already using vertx kafka client,
+A reactive kafka consumer (`quarkus-messaging-kafka`) will be subscribed to this topic and will change the status of the incoming events from `pending` to `completed`, and moving these records to `end-stock-price` topic.
+Note that there is another verticle `KStockPriceConsumer` launched by our verticle deployer, that does nothing. The reason is because `quarkus-messaging-kafka` is already using vertx kafka client,
so we don't really need a new verticle to consume Kafka in a reactive Non-blocking way. However, this verticle can be an example about how to deploy an abstract verticle from a verticle deployer.
[1]: https://vertx.io/docs/vertx-core/java/#_verticles
diff --git a/301-quarkus-vertx-kafka/pom.xml b/301-quarkus-vertx-kafka/pom.xml
index 22f521d0..48fa4581 100644
--- a/301-quarkus-vertx-kafka/pom.xml
+++ b/301-quarkus-vertx-kafka/pom.xml
@@ -27,7 +27,7 @@
io.quarkus
- quarkus-smallrye-reactive-messaging-kafka
+ quarkus-messaging-kafka