[jira] [Commented] (CAMEL-18497) camel-jbang - camel run -v x.y.z

["Tadayoshi Sato (Jira)" <ji...@apache.org>]

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

Tadayoshi Sato commented on CAMEL-18497:
----------------------------------------

[~squakez] [~davsclaus] Actually, JBang already allows specifying a branch or tag when installing an app:
{code}
jbang app install <alias>@<user/org>(/repository)(/branch)(~path)
{code}
https://www.jbang.dev/documentation/guide/latest/alias_catalogs.html#implicit-alias-catalogs
so you can already do:
{code}
jbang app install camel@apache/camel/camel-3.18.3
{code}
to use a specific version of Camel.

The problem is, though, in Camel side, where the {{CamelJBang}} at the {{camel-3.18.3}} still points to {{3.18.2}}. 
https://github.com/apache/camel/blob/camel-3.18.3/dsl/camel-jbang/camel-jbang-main/dist/CamelJBang.java
To make this version switch really available, the Camel release process would need to first update the {{CamelJBang}} and then do a release.

FYI [~acosentino]

> camel-jbang - camel run -v x.y.z
> --------------------------------
>
>                 Key: CAMEL-18497
>                 URL: https://issues.apache.org/jira/browse/CAMEL-18497
>             Project: Camel
>          Issue Type: Task
>          Components: camel-jbang
>            Reporter: Pasquale Congiusti
>            Priority: Minor
>             Fix For: 3.x
>
>
> We can specify any Camel version when using the jbang CLI as documented in: https://camel.apache.org/manual/camel-jbang.html#_using_a_specific_camel_version
> However, it would be nice to have the same feature when using directly camel CLI, in order to have the very same behavior.



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