luigidemasi opened a new issue, #25: URL: https://github.com/apache/camel-kit/issues/25
> Imported from [luigidemasi/camel-kit#44](https://github.com/luigidemasi/camel-kit/issues/44), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-04. > Closed by [luigidemasi/camel-kit#45](https://github.com/luigidemasi/camel-kit/pull/45), merged on 2026-05-04. --- ## Description Two checks to add to the `init` command for a better user experience. ### 1. Prerequisite detection Run during `init` and report what's installed vs missing: ``` Prerequisites: Java 17+ ✓ (21.0.3) JBang ✓ (0.119.0) Camel JBang ✓ (4.18.0) Camel test plugin ✗ (not found — /camel-verify will skip test phase) ``` Detection commands: - `java -version` — parse version, warn if < 17 - `jbang version` — check presence - `camel --version` — check Camel JBang is installed - `camel test --help` — check test plugin is installed Non-blocking: warn but don't fail. Design and planning phases work without Camel JBang. Only the execution and verification phases need it. ### 2. Overwrite detection Before writing files, check if the project directory already contains camel-kit artifacts: - `AGENTS.md` (universal — present for every agent) - `.camel-kit/` directory If found, prompt the user: "Project already initialized. Overwrite? [y/N]" Add a `--force` flag to skip the prompt: `camel-kit init my-project --ai claude --force` -- 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]
