davsclaus opened a new pull request, #27532:
URL: https://github.com/apache/camel/pull/27532
Some examples need something the run does not do: a model pulled into Ollama
(`ai/langchain4j-chat`), an API key (`ai/openai-pii-redaction`), or another
example running first (`contracts/openapi-client`). Without it they fail on
every message or at startup, and nothing said why before the run.
The example catalog carries what an example needs (`needs`), and the tools
now show it, so the user can do it by hand.
**camel run --example**
- Prints the needs before it starts the example:
```
Running example: contracts/openapi-client
Needs: contracts/openapi-server running first
```
- `camel run --example=<group>` lists them under each example, next to the
infra services.
**The monitor**
- The example browser shows a `needs:` line under the example.
- The notice when an example starts names the needs.
- The MCP tools that list and run examples return `needs`, so an agent can
tell the user (or do it).
**Catalog sync**
- The bundled catalog is synced from camel-jbang-examples, for the concrete
needs from apache/camel-jbang-examples#101. Only the catalog changed; the
bundled files did not.
Checked with `camel run --example=ai`, a run of `contracts/openapi-client`,
the example browser, and the MCP run tool, which returns `needs` with `failed`
for openai-pii-redaction without a key. ExampleHelperTest has a new case. All
1786 tests of the monitor plugin pass.
See apache/camel-jbang-examples#99.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
--
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]
