Hi Over the last week a number of Camel CLI changes have landed on main. They're groundwork for moving the CLI from picocli to aesh (CAMEL-23810):
- New camel-jbang-run module: camel run and camel export now run on one shared engine with a Java API. Other tools can run or export an integration without calling the CLI, and the run and export logic can't drift apart. - Exit codes follow Linux conventions: a file that doesn't exist now exits with 66 instead of 3. The exit codes page and the upgrade guide have the details. - Faster startup: camel version is down from about 920 ms to about 190 ms, and plugin commands from about 850 ms to about 150 ms in the installed distribution. - Command docs are generated from the command model, not by parsing the source, which fixed several doc pages. - New golden tests check what the CLI parses, prints and runs, so the aesh port won't change anything a user sees. Next is the aesh port itself. It's a clean break from picocli, so CLI plugins outside the Camel repo will need to move their commands to aesh. We'll share more when the port PR is up. Further out, this work is also a step towards native Camel CLI binaries for Windows, Linux and macOS. -- Claus Ibsen
