This is an automated email from the ASF dual-hosted git repository. luigidemasi pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit 90293a964be1404ab952d81d8827a3875914f767 Author: Luigi De Masi <[email protected]> AuthorDate: Mon Nov 16 13:42:56 2026 +0100 CAMEL-26926: Clarify unloaded Maven catalog version in 4.18 guide Co-authored-by: Codex <[email protected]> Signed-off-by: Luigi De Masi <[email protected]> --- docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc index 16021bbafe8e..4bbc681f44c7 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc @@ -918,6 +918,8 @@ Runtime dependency coordinates still use the selected Spring Boot or Camel Quark Versioned Main catalogs also report the selected version: `DefaultCamelCatalog.getCatalogVersion()` now honors the installed version manager instead of always reporting the built-in version. +When using `MavenVersionManager` from `camel-catalog-maven`, `getCatalogVersion()` returns `null` until +`loadVersion(...)` succeeds. A Quarkus BOM must identify both `org.apache.camel:camel-catalog` and `org.apache.camel.quarkus:camel-quarkus-catalog`. If either version or the selected catalog cannot be resolved,
