Support simple way to override/define the client version

quarkiverse / quarkus-artemis

Quarkus Artemis extensions

Apache License 2.0

12 stars 11 forks source link

Support simple way to override/define the client version #437

Open timonzi opened 4 months ago

timonzi commented 4 months ago

As you mentioned in #402, we can/should define the Artemis client version ourselves - normally by using the same version as for the broker.

It would be good to have a simple way to set the client version instead of overriding the dependency management (with all the exclusions) as described in this comment. For example: I don't know what exclusions might be required for an older or future client version.

It would be nice so have the possibility to set for example a Maven property which defines the client version. Also the import of a POM definition, which has the correct configuration per client could be a possibility.

turing85 commented 4 months ago

Some notes on this:

We'd want to have at least somewhat of a history for older versions of the driver. Looking at the releases at mvnrepository.com, maybe back to version 2.20.0
Whenever a new version of artemis is released, we need to build a new version of the bom
It would be ideal if the bom were maintained and released by activemq-artemis (github.com), @middagj, @zhfeng do you have contact to the artemis-team? Maybe they are willing to provide the bom.

zhfeng commented 4 months ago

I think there is https://github.com/apache/activemq-artemis/blob/main/artemis-bom/pom.xml just be added recently. Is it what you are expecting?

middagj commented 4 months ago

Yes, looks like it. I don't have any contacts with Artemis.