luigidemasi opened a new issue, #159: URL: https://github.com/apache/camel-kit/issues/159
Documentation follow-up for #110 (support selecting JBang or Camel Launcher). Replaces luigidemasi/camel-kit-web#56 now that the documentation lives in this repository (`docs/modules/ROOT/`, published at https://camel.apache.org/camel-kit/next/). ## What to document, once #110 is implemented - Installation and prerequisites: supported launcher and JDK versions, Kit plugin installation, and the `camel kit` command path without JBang (`getting-started.adoc`). - The explicit command-line switch for `jbang` versus `launcher`, the saved workspace choice and the detection of the actual `camel` implementation: switch precedence, behaviour when both are installed, and how to select an executable when detection is inconclusive. Launcher is not a fallback, JBang is not preferred merely because it is installed, and an unavailable selected backend must not switch silently (`commands.adoc`). - MCP startup for Catalog, Knowledge and Citrus when enabled: managed runner resolution and cache, repository and proxy settings, first-run network requirements (`mcp.adoc`, `knowledge.adoc`). - Camel Main execution, startup verification and the supported Citrus test path; launcher/project version mismatches and version-specific limitations. - Migration of existing JBang-based workspaces: regeneration, agent restart or reload, preservation of unrelated settings and permissions. - Troubleshooting through the prerequisite checks and `doctor`; offline cache requirements and actionable failures that do not recommend JBang as the only solution. - Keep the existing JBang path documented; align the Citrus wording with #109. ## Acceptance criteria - Options, defaults, server enablement and limitations match the shipped implementation; no claim that `camel mcp` is JBang-free for versions that still spawn JBang. - Examples work against the release that contains #110 and cover the operating systems where commands differ. - Getting started, command reference, MCP and Knowledge pages are consistent; the Antora build passes. - Documented in the same change as the feature, or linked from #110 before it closes. _AI-generated by Claude Fable 5.1 on behalf of @luigidemasi._ -- 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]
