This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/main by this push:
new 1be02de64 fix(doc): Camel dependencies catalog validation
1be02de64 is described below
commit 1be02de648a6eb78de67282d4d0c04f9fdd8e642
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Thu Sep 4 07:12:24 2025 +0200
fix(doc): Camel dependencies catalog validation
Closes #6218
---
docs/modules/ROOT/pages/configuration/dependencies.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/modules/ROOT/pages/configuration/dependencies.adoc
b/docs/modules/ROOT/pages/configuration/dependencies.adoc
index 56a002e27..259491157 100644
--- a/docs/modules/ROOT/pages/configuration/dependencies.adoc
+++ b/docs/modules/ROOT/pages/configuration/dependencies.adoc
@@ -60,11 +60,11 @@ kamel run -d camel:http Integration.java
In this case, the dependency will be added with the correct version. Note that
the standard notation for specifying a Camel dependency is `camel:xxx`, while
`kamel` also accepts `camel-xxx` for usability.
While resolving Camel dependencies (`camel:xxx` or `camel-xxx`) the Camel K
operator tries to find the dependency in the
xref:architecture/cr/camel-catalog.adoc[Camel catalog].
-In case the dependency is not listed in the catalog for some reason you will
be provided with am error.
-Please make sure to use Camel dependencies listed in the catalog as these
components are eligible to being used in Camel K (e.g. due to proper version
resolving and runtime optimization).
-Using Camel dependencies not listed in the catalog may lead to unexpected
behavior and is not supported.
-In case you do have a custom Camel component that you want to use as part of
an Integration you can add this as an external Maven dependency using the
respective Maven coordinates of your project.
-Please do not use one of the reserved the Camel groupIds (`org.apache.camel`)
in that case.
+In case the dependency is not listed in the catalog for some reason you will
be provided with an error. Please make sure to use Camel dependencies listed in
the catalog as these components are eligible to being used in Camel K (e.g. due
to proper version resolving and runtime optimization).
+
+Using Camel dependencies not listed in the catalog may lead to unexpected
behavior and is not supported. In case you do have a custom Camel dependency
that you want to use as part of an Integration you can add this as an external
Maven dependency using the respective Maven coordinates of your project.
+
+NOTE: altough not recommeded, you can use `mvn:org.apache.camel` group id to
skip the catalog validation in case of Camel dependencies not yet available in
the catalog. Mind that this may not always work.
*External dependencies* can be added using the `-d` flag, the `mvn` prefix,
and the maven coordinates:
```
