[
https://issues.apache.org/jira/browse/CAMEL-26766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Deppisch reassigned CAMEL-26766:
------------------------------------------
Assignee: Christoph Deppisch
> camel-jbang - Support custom plugin configuration path
> ------------------------------------------------------
>
> Key: CAMEL-26766
> URL: https://issues.apache.org/jira/browse/CAMEL-26766
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Christoph Deppisch
> Assignee: Christoph Deppisch
> Priority: Major
>
> All Camel JBang CLI instances on a machine share a single plugin
> configuration file at {{~/.camel-jbang-plugins.json}}. This causes conflicts
> when running multiple Camel CLI versions side by side or when developing and
> testing Camel JBang plugins, because every instance reads and writes the same
> file.
> The plugin mechanism should allow loading the plugin configuration from a
> custom location, for example via an environment variable or a command option
> ({{--plugin-config-path}}). When a custom path is specified, the CLI loads
> and persists plugin state there instead of the shared default location.
> This enables users to maintain separate plugin configurations per Camel CLI
> version or development workspace on the same machine.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
