You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2024/02/16 09:46:00 UTC
[jira] [Assigned] (CAMEL-20426) Camel Jbang execution - custom version precedences
[ https://issues.apache.org/jira/browse/CAMEL-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-20426:
-----------------------------------
Assignee: Claus Ibsen
> Camel Jbang execution - custom version precedences
> --------------------------------------------------
>
> Key: CAMEL-20426
> URL: https://issues.apache.org/jira/browse/CAMEL-20426
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Affects Versions: 4.3.0
> Reporter: Marco Carletti
> Assignee: Claus Ibsen
> Priority: Minor
> Attachments: commandsLog.txt
>
>
> according to the [documentation of the version command|https://camel.apache.org/manual/camel-jbang.html#_using_the_version_command] , the [specific camel version|https://camel.apache.org/manual/camel-jbang.html#_using_a_specific_camel_version] should have the precedence on the custom configuration.
> So I'm expecting that, even if I have the user configuration set with a specific camel version, running the command from CLI with an explicit version, the execution will be with the CLI one.
> So considering the command list:
> {code:bash}
> camel version set 4.0.1
> camel init cheese.xml
> camel run cheese.xml --camel-version=4.0.2
> {code}
> The expected running version is 4.0.2 but it is not, it is 4.0.1
> for the outputs I attach the [^commandsLog.txt]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)