You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pp...@apache.org on 2021/07/20 09:18:06 UTC

[camel-quarkus] branch main updated: Add information about BOMs and precedence of them (#2912)

This is an automated email from the ASF dual-hosted git repository.

ppalaga pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git


The following commit(s) were added to refs/heads/main by this push:
     new 8ef456d  Add information about BOMs and precedence of them (#2912)
8ef456d is described below

commit 8ef456d7f3bf5a7f65ac18f7d0a9877c85105ef1
Author: Martin Muzikar <46...@users.noreply.github.com>
AuthorDate: Tue Jul 20 11:17:58 2021 +0200

    Add information about BOMs and precedence of them (#2912)
    
    Add information about BOMs and their precedence
---
 docs/modules/ROOT/pages/user-guide/dependency-management.adoc | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/modules/ROOT/pages/user-guide/dependency-management.adoc b/docs/modules/ROOT/pages/user-guide/dependency-management.adoc
index 89ae3c0..c207e3c 100644
--- a/docs/modules/ROOT/pages/user-guide/dependency-management.adoc
+++ b/docs/modules/ROOT/pages/user-guide/dependency-management.adoc
@@ -2,6 +2,11 @@
 
 A specific Camel Quarkus release is supposed to work only with a specific Quarkus release.
 
+== Quarkus BOM 
+
+The core Quarkus dependencies are managed via `io.quarkus:quarkus-bom`. 
+This BOM doesn't manage the additional Quarkus extensions (Camel Quarkus, Kubernetes, ...), so there are other BOMs available for you to use in your projects that contain import `quarkus-bom`.
+
 == Quarkus Universe BOM
 
 The easiest and most straightforward way to get the dependency versions right is to use https://code.quarkus.io/[code.quarkus.io].
@@ -81,6 +86,9 @@ When combining `camel-quarkus-bom` or `quarkus-universe-bom` with any other BOM,
 think carefully in which order you import them,
 because the order of imports defines the precedence.
 
+I.e. if `my-foo-bom` is imported before `camel-quarkus-bom` then the versions defined in
+`my-foo-bom` will take the precedence. This might or might not be what you want, depending on whether there are any overlaps between `my-foo-bom` and `camel-quarkus-bom` and depending on whether those versions with higher precedence work with the rest of the artifacts managed in `camel-quarkus-bom`.
+
 == What's next?
 
 We recommend to continue with xref:user-guide/defining-camel-routes.adoc[Defining routes].