You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2026/03/13 08:33:00 UTC
[jira] [Assigned] (CAMEL-23150) camel-jbang - Be able to install and run camel-launcher as maven wrapper like
[ https://issues.apache.org/jira/browse/CAMEL-23150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet reassigned CAMEL-23150:
---------------------------------------
Assignee: Guillaume Nodet
> camel-jbang - Be able to install and run camel-launcher as maven wrapper like
> -----------------------------------------------------------------------------
>
> Key: CAMEL-23150
> URL: https://issues.apache.org/jira/browse/CAMEL-23150
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 4.x
>
>
> If you have different camel-jbang "projects" and you want to pin this to different camel versions, then it may desireable to lock down to a given camel version and be able to fully control this like you can do with maven wrapper.
> camel wrapper
> Then it installs itself into a .camel folder and installs camelw | camelw.cmd scripts like maven wrapper does.
> Then users can then just call camelw in that folder and it uses the intended camel version.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)