Closed cerasmus-booking closed 2 years ago
Hi @cerasmus-booking thanks for reporting this issue.
The incriminated artifact is io.quarkus:quarkus-vertx-core-deployment
and it has been removed in Quarkus 2.3. It has been replaced with io.quarkus:quarkus-vertx-deployment
.
In the Cassandra extension, we updated out main
branch accordingly, see https://github.com/datastax/cassandra-quarkus/commit/b1ffa41ea19ee223957423584f1a54f3545b2a57. But indeed we didn't release it yet.
You probably built the Cassandra extension using an old commit. Would you mind retrying with the latest commit from main? We fixed a somewhat related issue with quarkus-vertx
recently, see #204. You might be luckier trying that out.
As for the release, yes, we are going to release in the next days or so. Stay tuned!
Thanks, compiling against latest main
works. I'll use a self-compiled snapshot in the mean time until the release.
Hi @adutra , do you have a release date yet for 1.1.2
?
Hi @cerasmus-booking yes, we are aiming for this week! Stay tuned!
Hi, 1.1.2 has just been released. Thanks!
We are in the process of adding Quarkus extensions that include using Cassandra. However, our extensions are already on Quarkus 2.7.x and we will need to wait for the latest Quarkus Cassandra extension release.
The main problem is that using Quarkus 2.7 does not compile since there was a library change for
quarkus-vertx
:Pom:
I managed to compile a Cassandra Quarkus
1.1.2-SNAPSHOT
and have it successfully compile our extension. It looks like all that is needed is the1.1.2
release. If not, do you have a roadmap for when releases will be made?Verions: Quarkus: 2.7.1.Final Maven: 3.8.4 Java: 17.0.2
┆Issue is synchronized with this Jira Task by Unito