ppalaga opened a new issue #2136: URL: https://github.com/apache/camel-quarkus/issues/2136
Issues like #2131 are a clear sign that we are lacking on documentation about dependency management. Let me file a new issue for that. We should document at least: * The easiest and most straightforward option is to use https://code.quarkus.io/ producing a project with the `quarkus-universe-bom` that aggregates `camel-quarkus-bom`. This has the advantage that the user does not need to care for the compatibility of the individual artifacts that may potentially come from various independent project. All artifacts managed by `quarkus-universe-bom` is supposed to work together flawlessly. * Using `camel-quarkus-bom` instead of `quarkus-universe-bom`: As long as the user does not import any other BoM beyond `camel-quarkus-bom`, this is an easy and reliable option too. `camel-quarkus-bom` manages all supported Camel artifacts and it also imports `quarkus-bom`. This option can be used if the user plans to use only extensions from Quarkus and Camel Quarkus. * Combinig `camel-quarkus-bom` or `quarkus-universe-bom` with each other manually: does not make much sense because `camel-quarkus-bom` already imports a compatible version of `quarkus-universe-bom`. * Combinig `camel-quarkus-bom` with any other BoM: think carefully in which order you import them. The order of imports makes up the precedence. This matters for the artifacts managed by both BoMs. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
