luigidemasi commented on code in PR #29854: URL: https://github.com/apache/camel/pull/29854#discussion_r4566315253
########## docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc: ########## @@ -8046,6 +8046,25 @@ dead letter channel or a handled `onException`, so that the item is marked consu `delay`, or set `backoffIdleThreshold` and `backoffMultiplier`: a poll counts only the items that it marked consumed, so a poll whose items all failed is an idle poll, after which a `greedy` consumer does not poll again at once. +=== camel-jbang - runtime catalogs use the selected Camel version + +Spring Boot and Quarkus catalogs now report the resolved Camel core version and read EIP/model schemas from that +version's catalog. Previously, they could combine the selected runtime's component schemas with the running CLI or +MCP server's newer model schemas. A model absent from the selected catalog now remains absent. +Runtime dependency coordinates still use the selected Spring Boot or Camel Quarkus version. + +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, +catalog loading fails instead of returning the running server's catalog. Review Comment: Thanks for checking this. I verified the published platform BOMs, and 3.10.0 is not a minimum for the two catalog entries: - [quarkus-camel-bom 2.16.0.Final](https://repo.maven.apache.org/maven2/io/quarkus/platform/quarkus-camel-bom/2.16.0.Final/quarkus-camel-bom-2.16.0.Final.pom) contains `org.apache.camel:camel-catalog:3.20.1` and `org.apache.camel.quarkus:camel-quarkus-catalog:2.16.0`. - [quarkus-camel-bom 3.5.0](https://repo.maven.apache.org/maven2/io/quarkus/platform/quarkus-camel-bom/3.5.0/quarkus-camel-bom-3.5.0.pom) contains `org.apache.camel:camel-catalog:4.1.0` and `org.apache.camel.quarkus:camel-quarkus-catalog:3.5.0`. The production loader from `ada063404fd5` accepts the catalog-version metadata in both BOMs; I also checked 3.2.0.Final and 3.10.0. This probe checked metadata acceptance only, without attempting full runtime compatibility validation. The current exception already identifies the supplied BOM and both required catalog coordinates with non-empty versions. I’m keeping the existing coordinate-based requirement in the guide: adding the proposed minimum would incorrectly exclude older BOMs that contain the required entries. _AI-generated by Codex on behalf of @luigidemasi._ -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
