davsclaus opened a new issue, #86: URL: https://github.com/apache/camel-jbang-examples/issues/86
The CI build and the `camel` launcher most users have run the released Camel, 4.22.0 at the time of writing. Several examples were written against the 4.23 snapshot and had to be trimmed to what 4.22.0 supports. When 4.23.0 is out, revisit these: - **ai/mcp-server**: add `camel.server.mcp-server-title`, `camel.server.mcp-server-description` and `camel.server.mcp-instructions` to `application.properties` (only `mcp-enabled`, `mcp-tags` and `mcp-server-name` exist in 4.22.0), and mention MCP resources (`ai-resource` routes) in the README, which 4.23 serves next to tools. - **fail-well/circuit-breaker**: use `CamelCircuitBreakerResponseRejected` in the fallback and the new fallback/timeout/bulkhead counters in `camel get circuit-breaker`, see #81 (CAMEL-24818, CAMEL-24819). - **ai/langchain4j-chat**: once [CAMEL-24820](https://issues.apache.org/jira/browse/CAMEL-24820) lands, replace the `builderClass`/`builderMethod` bean with the simpler declaration it brings, and update the "How it works" text. - **contracts/openapi-server**: the contract's `servers` URL carries a base path (`/api`) because a URL without a path registers the operations but matches none of them on 4.22.0. On 4.23 both forms work; keep `/api`, but drop the sentence in the README saying the `servers` entry must have a path if 4.23 no longer needs it. - **Catalog and CLI**: check that `camel run --camel-version` is not needed anywhere, and that the `teaches` and `ciSkip` metadata are read by the 4.23 CLI listing of examples. Until then, run a new example with `camel run * --camel-version=4.22.0` before pushing, since that is what CI runs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj -- 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]
