Croway opened a new pull request, #22369: URL: https://github.com/apache/camel/pull/22369
# Description ``` $ CamelJBang --version 4.18.1 $ CamelJBang export --runtime=quarkus --name=test ... $ mvn dependency:tree | grep org.apache.camel [INFO] +- org.apache.camel.quarkus:camel-quarkus-core:jar:3.32.0:compile [INFO] | +- org.apache.camel:camel-base:jar:4.18.0:compile [INFO] | | +- org.apache.camel:camel-api:jar:4.18.0:compile ... ``` This is better than the actual behaviour, since without this fix Camel 4.17.0 is used by Quarkus. Once a Quarkus version with Camel 4.18.1 will be released, the `//JAVA_OPTIONS -Dcamel.jbang.quarkusVersion` version in these files should be updated. I looked into camel-launcher as well, but this cannot be easily done in camel-launcher, since the jar is shipped together with the release, eventually, we should decouple camel-launcher from Camel core and the Camel release... -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
