bvahdat commented on issue #4278: URL: https://github.com/apache/camel-quarkus/issues/4278#issuecomment-1317100008
Thanks @jamesnetherton that's actually what I have already tried out which solves the Camel version conflicts we have run into after the upgrade, but the problem is that there is no matching version of `quarkus-pooled-jms` and `quarkus-artemis` to be used along the way together with `Quarkus 2.13.4.Final`. - `quarkus-pooled-jms`: https://github.com/quarkiverse/quarkus-pooled-jms/blob/1.0.5/pom.xml#L23 - `quarkus-artemis`: https://github.com/quarkiverse/quarkus-artemis/blob/2.0.0/pom.xml#L32 The newer versions of the 2 extensions above make use of Quarkus `2.14.0.Final` which would push Camel `3.19.0` extensions into the classpath, a non-LTS version I don't want to go with. So you see the problem? I wan to stick to the same Quarkus version as for `camel-quarkus`, `quarkus-pooled-jms` and `quarkus-artemis` using the latest Camel LTS version, but this seems not to be possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
