Prepare for Quarkus 3.0.0

[turing85]

In the advent of the Quarkus 3.0.0 release, we should prepare this extension.

[middagj]

Great, let's wait for the first alpha and create a branch.

[zhfeng]

@middagj I find that you bump the version to 2.0.0 in the lastest release. So what is our stragtegy for the coming Quarkus 3? keep the main branch to align to Quarkus 3 and make 2.x branch for keeping support Quarkus 2.x?

[middagj]

Yes, that would be my proposal. Perhaps we can back port some features to the 2.x branch as well, but we won't do any major features.

The bump to 2.0.0 was to signal the changes in config.

[turing85]

@middagj I plan to make an alpha release so that extensions that are depending on us can test compatibility. Thought of releasing as 3.0.0.Alpha1. What do you think?

[middagj]

If you have the time it would be an excellent idea. Can you make the release on a separate branch and merge it once we get out of alpha?

[turing85]

I have a hunch that we can make a merge on the current feature branch, changing the version and everything should run. Will try it in a moment.

[turing85]

Yup, just worked. Release pipeline is running.

[turing85]

... welp...

[turing85]

This was a trip and a half. We have a Release 3.0.0.Alpha1 and 3.0.0.Alpha2 now (2 releases b/c something with the pipeline went wrong, that's also the reason why there is no tag for 3.0.0.Alpha1).

[turing85]

quarkus-pooled-jms cannot compile due to a version incompatibility of jarkarta.jms-api (we use 2.0.3 coming transitively from artemis-jms-client, quarkus-pooled-jms as well as quarkus-jta use 3.0.0).

I think we need a release of artemis-[core|jms]-client based on jakarta.jms-api version 3.0.0. @middagj can you confirm this? As of now, I see no way we can somehow "bridge" between two jakarta versions.

See quarkiverse/quarkus-pooled-jms#39 (comment) for details.

[zhfeng]

@turing85 Also it looks like we need to change to use org.apache.activemq:artemis-jakarta-client?

[turing85]

@zhfeng didn't know they had a separate client. This is probably the solution to the problem.

[middagj]

Is there any convention in Quarkus with respect to the import order of jakarta.*?

[turing85]

Not that I know of.

[turing85]

As of now, we cannot merge the "meat" of #121 into this branch since camel has not yet upgraded to quarkus 3. I have merged the non-essential parts (i.e. the test restructuring and the pipeline upgrades), but the rest can only be merged after we have a camel release that works with quarkus 3.

[zhfeng]

@turing85 @middagj Quarkus 3 has been out last week. Then I wonder if we need to bump our main branch to support Quarkus 3 and create a new branch quarkus-2.x to maintain Quarkus 2.16.x. As far as I know, there is no plan to release 2.17 with Quarkus.

[turing85]

@zhfeng 2.17 is in deed not planned. I see, however, no 3.0.0 release in mvnrepository, nor a 3.0.0 tag in github. Are you sure a final version is out?

[zhfeng]

@turing85 Are you going to do a new Alpha release of 3.0.0 after switching?

[turing85]

@zhfeng I did not plan to, no.

[turing85]

Starting the process now.

[turing85]

Switch is done.

[middagj]

Camel support was removed on purpose I recon. I didn't see anything strange, just Javadoc that got over 120 line width due to renaming.

[turing85]

Camel support was removed on purpose I recon. I didn't see anything strange, just Javadoc that got over 120 line width due to renaming.

Yes, the camel-parts were removed on purpose. See #154 for details.

As for the line length... is this not covered by the autoformatter?

[middagj]

No, apparently not. But fixed it.

[turing85]

Official release is on 2023-04-26 (groups.google.com). How about we build the 3.0.0 1 day before, i.e. on 2023-04-25?

[zhfeng]

@turing85 Can we release two days before because I also need to release quarkus-pooled-jms which depends on quarkus-artems-jms although it is just for testing.

[turing85]

So 2023-04-24 it is 🙂

[turing85]

Ad discussed with @zhfeng here, we decided to release on 2023-04-20.

[gsmet]

It's today so cool for me :).

Please ping me in the release PR, thanks!