[camel-quarkus] branch main updated: Remove the Camel Quarkus BOM section from the documentation

[al...@apache.org]

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

aldettinger 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 356c3d79da Remove the Camel Quarkus BOM section from the documentation
356c3d79da is described below

commit 356c3d79dae0b1e349a4b70dc9a0134150b46b79
Author: aldettinger <al...@gmail.com>
AuthorDate: Wed Apr 6 17:14:27 2022 +0200

    Remove the Camel Quarkus BOM section from the documentation
---
 docs/modules/ROOT/pages/user-guide/dependency-management.adoc | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/docs/modules/ROOT/pages/user-guide/dependency-management.adoc b/docs/modules/ROOT/pages/user-guide/dependency-management.adoc
index efe0182fcc..232a506608 100644
--- a/docs/modules/ROOT/pages/user-guide/dependency-management.adoc
+++ b/docs/modules/ROOT/pages/user-guide/dependency-management.adoc
@@ -81,15 +81,6 @@ This has the advantage that application developers do not need to care for the c
 that may come from various independent projects.
 Note that not all combinations of artifacts managed by the various BOMs are tested.
 
-== Camel Quarkus BOM
-
-As long as you do not plan to use any dependencies beyond those from Quarkus and Camel Quarkus,
-you may consider switching to `org.apache.camel.quarkus:camel-quarkus-bom`.
-It manages all supported Camel artifacts and imports `io.quarkus:quarkus-bom`.
-
-NOTE: `io.quarkus:quarkus-bom` manages the core Quarkus dependencies,
-such as `io.quarkus:quarkus-arc` (CDI), `io.quarkus:quarkus-hibernate-orm`, `io.quarkus:quarkus-resteasy` (JAX-RS), etc.
-
 == Combining with other BOMs
 
 When combining `camel-quarkus-bom` with any other BOM,