ammachado opened a new pull request, #24915: URL: https://github.com/apache/camel/pull/24915
# Description Adds JReleaser-driven package distribution for the `camel-launcher` module, generating installable packages for five package managers: Homebrew, SDKMAN, WinGet, Scoop, and Chocolatey. - `jreleaser.yml` configures the distribution definitions and custom templates under `src/jreleaser/distributions/camel-cli/<packager>/`. - `camel-package.sh` / `camel-package.bat` wrap the JReleaser Maven plugin invocation as user-facing entry points. - The JReleaser plugin is bound with `<inherited>false</inherited>` and no lifecycle phase, so ordinary Camel builds are unaffected; only the wrapper scripts invoke its goals explicitly. - WinGet ships the native `camel-x64.exe` / `camel-arm64.exe` bootstraps (from the merged `tooling/camel-exe` cross-compile work); Chocolatey and Scoop use `camel.bat` as their entry point instead and strip the exe files from their packages. - Homebrew URLs use the `search.maven.org/remotecontent` redirector per Homebrew's `FormulaAudit::Urls` rubocop, rather than `repo1.maven.org` directly (documented in the module README). - Chocolatey runs x64 via `camel.bat` on both x64 and ARM64 Windows until native ARM64 support lands in Chocolatey ([chocolatey/choco#1803](https://github.com/chocolatey/choco/issues/1803)). - `license-maven-plugin` excludes were added for the new `.tpl`/`.bat` template files, whose extensions or lack of comment syntax (JSON) aren't compatible with automatic header formatting; each exclude is documented inline in the pom. This is part 3 of the split of the original CAMEL-23703 unified Camel CLI packaging work (see #24682, #24754, #24665, #24664). It targets `apache/camel` `main` and does not depend on unmerged content from any other part of the split — it was verified to build and test standalone. # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL-23703) filed for the change (usually before you start working on it). # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. # AI-assisted contributions - [x] If this PR includes AI-generated code, commits have proper co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR description identifies the AI tool used. _Claude Code on behalf of Adriano Machado (ammachado)_ -- 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]
