Upgrade to Quarkus 2.0

[adutra]

The extension currently cannot be compiled against Quarkus 2.0, see https://github.com/quarkusio/quarkus/issues/8593#issuecomment-844722003.

Things to fix:

• A few classes do not compile anymore, mostly due to Vert.x API changes.
• MicroProfile 3.0 is not binary-compatible with 2.x; this requires changes in the driver, see JAVA-2944.
• It turns out that compilation of the extension with Java 11 unveiled Yet-Another-Cryptic-Class-Loading-Problem with the driver's usage of the ServiceLoader API. I opened JAVA-2946 to fix that (or find a workaround). On the extension side, this is likely to require #171 as well.

┆Issue is synchronized with this Jira Task by Unito

[adutra]

Also, it would be fair to keep compatibility with Quarkus 1.x and 2.x for some time. I suggest that we keep the 1.0.x series for bugfixes targeting Quarkus 1.x, and create a minor version 1.1.0 along with a new 1.1.x branch to host future improvements and bugfixes targeting Quarkus 2.x.

[aloubyansky]

Sounds good.

[adutra]

@ppalaga 1.1.0-rc1 is available from Maven Central. Do you need me to upgrade quarkus-platform or can you do it? Thanks!

[aloubyansky]

@adutra do you already have a date for the final?

[aloubyansky]

Are the tests listed https://github.com/quarkusio/quarkus-platform/blob/main/pom.xml#L248 looking good to you?

[adutra]

@adutra do you already have a date for the final?

We were planning to have our 1.1.0 GA depend on Quarkus 2.0.0.Final. Is that a problem? I guess we are in a classic chicken-and-egg problem :-)

Are the tests listed https://github.com/quarkusio/quarkus-platform/blob/main/pom.xml#L248 looking good to you?

Wow this is totally new to me. But yes, the artifacts listed there are 100% correct.

[aloubyansky]

@adutra do you already have a date for the final?

We were planning to have our 1.1.0 GA depend on Quarkus 2.0.0.Final. Is that a problem? I guess we are in a classic chicken-and-egg problem :-)

Sure, that makes sense. The Quarkus core 2.0.0.Final release is scheduled on June 23rd and the platform release on June 30th. It'd be great if you could release in time for the platform release.

Are the tests listed https://github.com/quarkusio/quarkus-platform/blob/main/pom.xml#L248 looking good to you?

Wow this is totally new to me. But yes, the artifacts listed there are 100% correct.

Are you subscribed to https://groups.google.com/g/quarkus-platform-coordination ? This is where we announce and coordinate changes and releases. (Also see https://groups.google.com/g/quarkus-platform-coordination/c/NxR3kFzowd0)

[adutra]

The Quarkus core 2.0.0.Final release is scheduled on June 23rd and the platform release on June 30th. It'd be great if you could release in time for the platform release.

That can work, I will plan our release to the 24th.

Are you subscribed to https://groups.google.com/g/quarkus-platform-coordination ?

In fact I am and I was aware of the changes at hand, only I haven't really payed attention to how things are shaped now.

[aloubyansky]

Great, thanks!

[ppalaga]

@ppalaga 1.1.0-rc1 is available from Maven Central.

Thanks for the release, let me test inside Camel Quarkus first.

Do you need me to upgrade quarkus-platform or can you do it?

Sounds like @aloubyansky did it already?

[aloubyansky]

@ppalaga 1.1.0-rc1 is available from Maven Central.

Thanks for the release, let me test inside Camel Quarkus first.

Do you need me to upgrade quarkus-platform or can you do it?

Sounds like @aloubyansky did it already?

I haven't.

[adutra]

@ppalaga 1.1.0-rc1 is available from Maven Central.

Thanks for the release, let me test inside Camel Quarkus first.

Do you need me to upgrade quarkus-platform or can you do it?

Sounds like @aloubyansky did it already?

I haven't.

Will do it today.

[ppalaga]

Any ETA of a release with Quarkus 2.0.0.Final, @adutra ?