[ 
https://issues.apache.org/jira/browse/CAMEL-23703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097594#comment-18097594
 ] 

Adriano Machado commented on CAMEL-23703:
-----------------------------------------

Status update on the pieces of this ticket:

|| Component || Status ||
| Java runtime discovery for camel.sh/camel.bat | Merged (apache/camel#24664) |
| Native camel.exe bootstrap (Windows) | Merged (apache/camel#24665) |
| Cross-compile camel.exe for x64/arm64 | Merged (apache/camel#24754) |
| Website installer scripts (install.sh/install.ps1) + release manifests | 
Merged (apache/camel#24682) |
| JReleaser packaging (Homebrew, SDKMAN, WinGet, Scoop, Chocolatey) | Open, in 
review (apache/camel#24915) |
| Package-native validation CI (installs/uninstalls each generated package and 
smoke-tests it) | Prepared; PR will follow once #24915 merges |

Not yet started:

* *Actual publishing to the package managers.* Everything above only 
prepares/packages the artifacts locally; nothing pushes a release to Homebrew, 
SDKMAN, WinGet, Scoop, or Chocolatey yet. This needs a PMC decision on publish 
destinations first, e.g. whether Homebrew formulae go to this project's own tap 
or to homebrew-core, since that decision shapes how publishing gets wired up. 
It also blocks producing both the unversioned and versioned Homebrew formula 
from a single release.
* *Making install.sh/install.ps1 reachable at camel.apache.org.* The scripts 
are done and tested, but nothing serves them yet, so {{curl -fsSL 
https://camel.apache.org/install.sh}} doesn't resolve. That requires a change 
in the camel-website repo; the tracking issue there (camel-website#1487) is 
still open with no PR against it.

> camel-cli - Distribute release to various 3rd-party package managers
> --------------------------------------------------------------------
>
>                 Key: CAMEL-23703
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23703
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Adriano Machado
>            Priority: Major
>             Fix For: 4.22.0
>
>
> [https://github.com/apache/camel-website/issues/1487]
> We should look at if we can make camel cli distibuted to various places such 
> as brew, skdman and what else is out there, and also have install scripts on 
> camel website - especially for camel launcher which is a single installer 
> with local scripts (no jbang).
> JRelease as a project has various support for this.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to