You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Vinod Pahuja (Jira)" <ji...@apache.org> on 2022/08/30 07:55:00 UTC
[jira] [Commented] (CAMEL-18425) camel-cli - Make regular Camel applications work with Camel CLI
[ https://issues.apache.org/jira/browse/CAMEL-18425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597644#comment-17597644 ]
Vinod Pahuja commented on CAMEL-18425:
--------------------------------------
Is it wise to abstract camel-cli to a parent dependency having implementation using different runtime ?
like one we already have using jbang and another could be implemented using spring-boot-cli
I tried to run a standalone camel route using spring-boot-cli and it just works fine but still need some operational fine tuning.
https://github.com/apache/camel-spring-boot-examples/pull/79
> camel-cli - Make regular Camel applications work with Camel CLI
> ---------------------------------------------------------------
>
> Key: CAMEL-18425
> URL: https://issues.apache.org/jira/browse/CAMEL-18425
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.19.0
>
>
> The Camel CLI has commands to get status and start/stop camel applications, but its limited to camel-jbang based integrations.
> We can look at having a camel-cli dependency that you can add to camel-spring-boot or camel-main etc when you want your app to be able to work with the Camel CLI.
> This dependency should only be used for development purposes.
> You could then have a mvn spring-boot:run app and then also a camel-jbang app that work together and you need to control them via the camel cli, to have a better UX.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)