Upgrade the examples to Camel 4.23 once it is released

Closed
  • Is something wrong?
#86 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
cli, documentation, tooling

Research direction

After Camel 4.23.0 is released, inspect the listed example directories, their application.properties and README files, plus the Catalog and CLI metadata. Start by running a new example with camel run * --camel-version=4.22.0, then verify the documented MCP, circuit-breaker, LangChain4j, OpenAPI, and metadata changes against 4.23. Done means the examples and README text use the new release while CI remains consistent.

Written by the indexing model from the issue text.

Description

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 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.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj

Dominant language
HTML
Stars
15
Forks
15
Avg merge
10h 47m
Merged PRs (30d)
27

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/camel-jbang-examples

All issues in apache/camel-jbang-examples

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.