Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change Quarkus reactive messaging artifact names #507

Merged
merged 1 commit into from
Sep 6, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions 002-quarkus-all-extensions/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-smallrye-reactive-messaging-kafka</artifactId>
<artifactId>quarkus-messaging-kafka</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
Expand Down Expand Up @@ -154,7 +154,7 @@
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-smallrye-reactive-messaging-amqp</artifactId>
<artifactId>quarkus-messaging-amqp</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
Expand Down Expand Up @@ -198,7 +198,7 @@
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-smallrye-reactive-messaging</artifactId>
<artifactId>quarkus-messaging</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
Expand Down Expand Up @@ -367,7 +367,7 @@
<!-- </dependency>-->
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-smallrye-reactive-messaging-mqtt</artifactId>
<artifactId>quarkus-messaging-mqtt</artifactId>
</dependency>
<!-- New extensions in 1.7.1 comparing to 1.3.4 -->
<!-- <dependency>-->
Expand Down
6 changes: 3 additions & 3 deletions 003-quarkus-many-extensions/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-smallrye-reactive-messaging-amqp</artifactId>
<artifactId>quarkus-messaging-amqp</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
Expand Down Expand Up @@ -119,7 +119,7 @@
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-smallrye-reactive-messaging-kafka</artifactId>
<artifactId>quarkus-messaging-kafka</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
Expand All @@ -135,7 +135,7 @@
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-smallrye-reactive-messaging</artifactId>
<artifactId>quarkus-messaging</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
Expand Down
4 changes: 2 additions & 2 deletions 301-quarkus-vertx-kafka/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion 301-quarkus-vertx-kafka/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-smallrye-reactive-messaging-kafka</artifactId>
<artifactId>quarkus-messaging-kafka</artifactId>
</dependency>
<!-- Kafka -->
<dependency>
Expand Down
Loading