luigidemasi opened a new pull request, #29854: URL: https://github.com/apache/camel/pull/29854
Fixes [CAMEL-26926](https://issues.apache.org/jira/browse/CAMEL-26926). Spring Boot and Quarkus catalog requests for Camel 4.8.0 could return the running server's version and EIP schemas alongside the selected runtime's component schemas. The shared JBang loaders now isolate catalog resources from the server classpath and report the resolved Camel core version separately from the runtime provider version. Provider classes continue to share the running catalog API. Quarkus loads the core catalog selected by its BOM and rejects missing version/artifact metadata. Spring Boot retains its existing fallback for releases whose version differs from Camel core. The upgrade guide describes the corrected lookup behavior. Validation: - Full 722-module reactor: `./mvnw -B -ntp clean install -DskipTests -Dmaven.build.cache.enabled=false` passed, with no unrelated generated changes. - `camel-jbang-run`: 276 tests passed, including byte comparisons against the selected artifacts and missing-resource checks. - `camel-jbang-mcp`: 545 tests passed, including Spring Boot with/without a BOM, explicit Quarkus BOM selection, and repeated mixed-runtime requests. - The MCP runner produced by the full build passed 10 stdio tool calls; all 1,923 returned schemas matched the selected core/provider artifacts byte for byte. - Reintroducing parent-first lookup or fallback-on-miss separately caused the regression test to fail on schema content. Generated by Codex on behalf of @luigidemasi via /oss-fix-issue. -- 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]
