DBZ-6129 Upgrade to Quarkus 3.0.0.Final #4299
Conversation
Naros
force-pushed
the
DBZ-6129
branch
2 times, most recently
from
86ea979
to
24ab7d4
Compare
|
The |
|
@ani-sha is there a reason why |
Naros
force-pushed
the
DBZ-6129
branch
6 times, most recently
from
39f5b3e
to
e32855a
Compare
|
@Naros Do you know if we can expect a debezium release using Quarkus 3.0.0.CR1 or CR2 version? Or will debezium only release after Quarkus 3.0.0.Final is released? |
|
@spieps We aim for a release with Quarkus 3.0.0.Final at the end of this week. |
|
Hi @spieps, Quarkus 3.0.0.Final was just released today and I am preparing the PRs based on that release. Once we have the PRs completely buildable and green they'll be merged and Debezium 2.2.0.CR1 will be based on Quarkus 3. Our goal is then to release Debezium 2.2.0.Final next week and to bundle Quarkus 3 Platform with Debezium 2.2. |
Quarkus 3 now includes Jakarta EE which replaces the old Java EE classes that were found within the `javax.*` package and are now in `jakarta.*`.
Quarkus 3 now includes Jakarta EE which replaces the old Java EE classes that were found within the `javax.*` package and are now in `jakarta.*`. In addition, quarkus-boostrap-maven-plugin had been deprecated and is no longer available, replaced with quarkus-extension-maven-plugin instead with the CR1 release of Quarkus 3.
|
Amazing!! Thank you all so much for this! |
https://issues.redhat.com/browse/DBZ-6129
OutboxIT(reactive/non-reactive) test failure, attempting to use CDI beans, which is no longer supported.debezium-serverrepository to Quarkus 3 (DBZ-6129 Upgrade to Quarkus 3.0.0.Final debezium-server#8)