gnodet-bot commented on code in PR #29854: URL: https://github.com/apache/camel/pull/29854#discussion_r4566177487
########## 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: The upgrade guide states that a Quarkus BOM must include both `org.apache.camel:camel-catalog` and `org.apache.camel.quarkus:camel-quarkus-catalog`, but doesn't indicate the minimum BOM version where this holds. Users on older Quarkus releases will hit `Cannot determine Camel and Camel Quarkus catalog versions` with no hint of why. Based on published platform BOMs, `quarkus-camel-bom` reliably includes `org.apache.camel:camel-catalog` from 3.10.0 onwards. Consider adding a note: ```suggestion A Quarkus BOM must identify both `org.apache.camel:camel-catalog` and `org.apache.camel.quarkus:camel-quarkus-catalog`. This requires Quarkus Platform BOM 3.10.0 or later. If either version or the selected catalog cannot be resolved, ``` -- 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]
