[
https://issues.apache.org/jira/browse/CAMEL-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638555#comment-17638555
]
Claus Ibsen commented on CAMEL-18497:
-------------------------------------
However coming back to your original inspection. I think its a good first
solution to make a Camel release have the correct version in the source file,
so you can install it via jbang app and provide the version.
Maybe we can use a maven profile (release) so when a release is built this
maven profile is activated and it does a version replacement, like maven does
when it replaces all the pom.xml from -SNAPSHOT to the actual version.
And if we dont have time before 3.18.4, we can hardcode that version in the
source today, so its correct when release.
> 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)
