[
https://issues.apache.org/jira/browse/CAMEL-26455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-26455.
---------------------------------
Resolution: Fixed
> camel-jbang - camel config set dev=true does not set the --dev option of
> camel run
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-26455
> URL: https://issues.apache.org/jira/browse/CAMEL-26455
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> A default from the user configuration (camel config set) is only looked up by
> the longest name of an option. The --reload,--dev option of camel run is
> therefore set by reload=true, but dev=true (or camel.run.dev=true) is
> silently ignored. The same goes for every option with more than one long
> name, such as --dep,--dependency and --dir,--directory.
> Found with the golden test of what the CLI parses (CAMEL-23810), together
> with two option definitions to clean up before the port from picocli to aesh:
> * camel dependency update declares its own positional files, and also
> inherits the <files> of the export. picocli gives the files to both, and the
> command relies on that. A parser that fills only one of them (as aesh does)
> leaves the export without its source files.
> * camel dependency copy: --output-directory is required and has a default
> value (lib). The default already satisfies picocli, so required does nothing.
> _Claude Code on behalf of davsclaus (Claus Ibsen)_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
