[GitHub] [camel-quarkus] jamesnetherton commented on issue #4278: The used Quarkus version in camel-quarkus 2.13.1

2022-11-16 Thread GitBox
jamesnetherton commented on issue #4278: URL: https://github.com/apache/camel-quarkus/issues/4278#issuecomment-1318115861 > 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 Usually you would impor

[GitHub] [camel-quarkus] jamesnetherton commented on issue #4278: The used Quarkus version in camel-quarkus 2.13.1

2022-11-16 Thread GitBox
jamesnetherton commented on issue #4278: URL: https://github.com/apache/camel-quarkus/issues/4278#issuecomment-1316967419 > So are you suggesting to better make use of Quarkus 2.13.4.Final together with camel-quarkus:2.13.1? Yes. If you import `io.quarkus.platform:quarkus-camel-bom:2.

[GitHub] [camel-quarkus] jamesnetherton commented on issue #4278: The used Quarkus version in camel-quarkus 2.13.1

2022-11-16 Thread GitBox
jamesnetherton commented on issue #4278: URL: https://github.com/apache/camel-quarkus/issues/4278#issuecomment-1316944070 > So shouldn´t camel-quarkus:2.13.1 declare Quarkus 2.13.4.Final as it´s target runtime? `2.13.4.Final` was not available at the time at which the release was tagg