Each Camel K end user application has a Maven project associated with it. This Maven project is held for an internal Camel K implementation detail and end users do not have a direct access to the pom.xml file defining the project.

This pom.xml file currently imports (directly or indirectly) org.apache.camel.quarkus:camel-quarkus-bom to manage all relevant Camel, Camel Quarkus and Quarkus artifacts.

This feature request aims at replacing org.apache.camel.quarkus:camel-quarkus-bom with BOMs from Quarkus Platform, namely

• com.redhat.quarkus.platform:quarkus-bom
• com.redhat.quarkus.platform:quarkus-camel-bom

These two BOMs manage the same artifacts as org.apache.camel.quarkus:camel-quarkus-bom.

Why this change is necessary:

1. Security fixes: Some security fixes in Quarkus artifacts and their transitive dependencies will only be available via Quarkus Platform.
2. Quarkus team plans to stop releasing the productized version of io.quarkus:quarkus-bom to the public Maven GA repository starting with Quarkus 2.7.0 (code name Elektra) - see QUARKUS-1770 . This will make the productized org.apache.camel.quarkus:camel-quarkus-bom unusable, because it depends on io.quarkus:quarkus-bom.

Timeframe:

CEQ 2.7.0 will depend on Quarkus 2.7.0 Elektra, thus the change in Camel K will have to happen with the upgrade to CEQ 2.7.0.

Related issues:

• Camel Quarkus upstream: https://github.com/apache/camel-quarkus/issues/3347
• Related changes in CEQ 2.2.1 https://issues.redhat.com/browse/ENTESB-17875