This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch feature/CAMEL-23722-cli-docs-restructure in repository https://gitbox.apache.org/repos/asf/camel.git
commit 491227d5ef518d59ddf767589d1c67282b53703a Author: Claus Ibsen <[email protected]> AuthorDate: Tue Jun 9 20:11:17 2026 +0200 CAMEL-23722: Tighten Launcher page prose (79 -> 53 lines) Co-Authored-By: Claude <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- .../modules/ROOT/pages/camel-jbang-launcher.adoc | 43 +++++----------------- 1 file changed, 9 insertions(+), 34 deletions(-) diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-launcher.adoc b/docs/user-manual/modules/ROOT/pages/camel-jbang-launcher.adoc index d2700d011e4f..05de148c52c0 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-jbang-launcher.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-launcher.adoc @@ -2,25 +2,12 @@ *Available as of Camel 4.13* -This module provides a self-contained executable JAR that includes all dependencies required to run Camel CLI without the need for the JBang two-step process. +A self-contained executable JAR for running Camel CLI without JBang. Uses Spring Boot's nested JAR loader for fast startup and isolated classpath. -The launcher uses Spring Boot's loader tools to create a self-executing JAR with a nested structure, similar to Spring Boot's executable JARs. This provides better performance and avoids classpath conflicts compared to traditional fat JARs. - -== Downloading - -You can download the `camel-launcher` JAR from https://repo1.maven.org/maven2/org/apache/camel/camel-launcher/[Maven Central]. +Download from https://repo1.maven.org/maven2/org/apache/camel/camel-launcher/[Maven Central]. == Using the fat-jar directly -Then you can run the JAR using standard Java as follows: - -[source,bash] ----- -java -jar camel-launcher-<version>.jar [command] [options] ----- - -For example: - [source,bash] ---- java -jar camel-launcher-<version>.jar version @@ -49,29 +36,17 @@ And then use the provided scripts: bin\camel.bat [command] [options] ---- -== Benefits of using Camel Launcher +== Benefits -- No need for JBang installation -- Single executable JAR with all dependencies included -- Faster startup time (no dependency resolution step, on-demand class loading) -- Better memory usage (only loads classes that are actually used) -- Avoids classpath conflicts (dependencies kept as separate JARs) -- Each self-executing JAR is its own release, avoiding version complexity -- Can still be used with JBang if preferred -- Locked to use pinned version of Camel which is the same version as the launcher; to upgrade, then download and use a newer launcher. +- No JBang installation required +- Faster startup (no dependency resolution, on-demand class loading) +- Lower memory usage (only loads classes actually used) +- No classpath conflicts (dependencies kept as separate nested JARs) +- Pinned Camel version — upgrade by downloading a newer launcher == Limitations -The following features are not supported when running from camel-launcher: - -=== --camel-version option - -The `--camel-version` option requires JBang to dynamically download and run a different Camel version. - -Alternatives: - -- Use a different camel-launcher JAR version -- Install Camel CLI via JBang: `jbang app install camel@apache/camel` +The `--camel-version` option is not supported — it requires JBang to dynamically download a different version. Use a different launcher JAR version instead, or install via JBang: `jbang app install camel@apache/camel`. == More Information
