[
https://issues.apache.org/jira/browse/CAMEL-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638498#comment-17638498
]
Claus Ibsen edited comment on CAMEL-18497 at 11/25/22 5:39 AM:
---------------------------------------------------------------
Yeah that is only a half solution as then the CLI would also be downgraded.
What we want is to separate the CLI and run (however this is also a bigger
task).
After installing a given version you can edit the
~.jbang/cache/urls/f20491f9ebc0e16d2fca028eb3d4f03aafdf8cd62b8af1a9d1730bfe382d8165/CamelJBang.java
file and change the version there, the hash is the same, so you can also have a
script that does this afterwards. Or a new command in camel jbang itself ;)
was (Author: davsclaus):
Yeah that is only a half solution as then the CLI would also be downgraded.
What we want is to separate the CLI and run
> 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)
