davsclaus opened a new pull request, #30127:
URL: https://github.com/apache/camel/pull/30127
## What
The Camel CLI distribution (`camel-launcher`) has the jar of
`camel-jbang-plugin-mcp`, but `CamelLauncherMain` didn't list the plugin among
its embedded plugins, next to `generate`, `kubernetes`, `tui`, `validate` and
`test`. So:
- the first `camel mcp` installed it like a plugin to download: it printed
`Installed plugin: mcp` and wrote an entry to `~/.camel-jbang-plugins.json`
- `camel --help` listed `mcp` under "Plugins (not installed)"
Now `mcp` is an embedded plugin, and `camel mcp` creates only its own
command, as the other embedded plugins do since #28774. Nothing in the history
(shallow) or JIRA says it was left out on purpose. It was never in the list,
not even before #28774.
A user whose `~/.camel-jbang-plugins.json` already has `mcp` from an earlier
`camel mcp` is not affected: `PluginHelper` skips a configured plugin whose
command is already registered.
## Tests
- `CamelLauncherTest`:
- `camel mcp --help` creates only the `mcp` command
- `camel --help` has the commands of all embedded plugins, now with `mcp`,
`validate` and `test`
Both fail with the old `CamelLauncherMain`.
- A launcher built from this branch, in a fresh home: `camel mcp --help`
exits 0 with no `Installed plugin` line and writes no plugin configuration, and
`camel --help` lists `mcp` with the commands.
_Claude Code on behalf of Claus Ibsen (davsclaus)_
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]