davsclaus opened a new pull request, #77: URL: https://github.com/apache/camel-jbang-examples/pull/77
One tool to learn: the Camel CLI. Its test plugin runs the Citrus YAML tests (`camel test run`, resolving Citrus at the version camel-parent pins, 5.0.1 today), so the examples stop asking for a second CLI. - The CI workflow installs the test plugin and runs `camel test run <example>/test` instead of the standalone Citrus JBang application; the Citrus trust and install steps go. - Every README that mentioned `citrus run` or the Citrus install page now says `camel test run test/<name>.citrus.it.yaml`; the contributor guide says the same. - `install-citrus.adoc` only explained the second tool and is removed. Checked locally with the CLI: the three rung-1 tests, and the container-backed MQTT test, which starts and stops its compose file through `camel test run` and leaves nothing running. `camel test run <dir>` also works, as the workflow uses it. Independent of #76 (rung 1), which already documents `camel test run` for its own examples. 🤖 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]
