-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manage camel-quarkus-catalog in camel-quarkus-bom to allow Camel K to use Quarkus Platform BOMs #3347
Labels
Comments
ppalaga
changed the title
Allow Camel K to use Quarkus Platform BOMs
Manage camel-quarkus-catalog in camel-quarkus-bom to allow Camel K to use Quarkus Platform BOMs
Jan 26, 2022
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Jan 26, 2022
use Quarkus Platform BOMs apache#3347
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Jan 26, 2022
use Quarkus Platform BOMs apache#3347
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Jan 26, 2022
… use Quarkus Platform BOMs apache#3347
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Jan 26, 2022
… use Quarkus Platform BOMs apache#3347
ppalaga
added a commit
to jboss-fuse/camel-quarkus
that referenced
this issue
Jan 26, 2022
… use Quarkus Platform BOMs apache#3347
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It might be practical for Camel K to rely on Quarkus Platform BOMs instead of Camel Quarkus BOM, mainly to be able to consume security updates that are available only via Quarkus Platform.
To make this possible, we need to:
1. Manage org.jooq:joor in Camel Quarkus BOM2. Pass camel-quarkus-integration-test-java-joor-dsl to the platform in spite it is JVM-only (the platform will have to be able to handle the fact)Edit: I do not thing points 1. and 2. were ever needed. I made some false assumptions about how the dependency management works in the platform. Sorry for the confusion.
The text was updated successfully, but these errors were encountered: