[
https://issues.apache.org/jira/browse/CAMEL-25718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-25718 started by Claus Ibsen.
-------------------------------------------
> camel-jbang - Document the commands of camel test that come from Citrus
> -----------------------------------------------------------------------
>
> Key: CAMEL-25718
> URL: https://issues.apache.org/jira/browse/CAMEL-25718
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang, tooling
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Seven of the nine commands of the {{camel test}} plugin have no page in the
> Camel CLI command reference: {{camel test inspect}}, {{test run}}, {{test
> ps}} (alias {{ls}}), {{test agent}}, {{test agent start}}, {{test agent run}}
> and {{test agent stop}}. The plugin registers these commands of Citrus as
> they are ({{org.citrusframework.jbang.cli.commands.Run}} and so on), and
> {{PrepareCamelJBangCommandsMojo}} only documents a command whose class has a
> source in the module, so it leaves them, and the subcommands of {{camel test
> agent}}, out. All other commands (camel-jbang-core and the other plugins) are
> documented.
> Since CAMEL-25717 the generator reads the options of a library class from the
> classpath of the project. It can document these commands the same way: the
> command class imported by name by the source that registers it, its
> {{@Command}} (description, hidden) and its options read by reflection.
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
