[
https://issues.apache.org/jira/browse/CAMEL-23478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-23478:
--------------------------------
Fix Version/s: 4.x
> Add install scripts to camel-launcher distribution archive
> ----------------------------------------------------------
>
> Key: CAMEL-23478
> URL: https://issues.apache.org/jira/browse/CAMEL-23478
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Affects Versions: 4.20.0
> Reporter: Federico Mariani
> Assignee: Adriano Machado
> Priority: Minor
> Fix For: 4.x
>
>
> The camel-launcher distribution (zip/tar.gz) currently ships the JAR and run
> scripts ({{camel.sh}}/{{camel.bat}}), but users must manually copy JARs,
> create wrapper scripts, configure PATH, and handle platform-specific details
> (e.g., macOS quarantine). This creates friction for new users and makes
> upgrades error-prone.
> h3. Proposal
> Ship {{install.sh}} (Linux + macOS) and {{install.cmd}} (Windows) in the
> distribution archive root. Running the installer automates the full setup:
> - Verifies Java 17+ is available
> - Copies the JAR to a canonical location ({{~/opt/camel/}} on Unix,
> {{%LOCALAPPDATA%\Camel}} on Windows) with a stable name for easy upgrades
> - Creates a wrapper script in a standard user bin directory ({{~/bin/}} on
> macOS, {{~/.local/bin/}} on Linux, {{%LOCALAPPDATA%\Camel}} on Windows)
> - Adds the bin directory to PATH if not already present
> - Detects existing JBang-based Camel installs and suggests cleanup
> - Handles re-runs for upgrades (replaces JAR, avoids duplicate PATH entries)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
