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 2015/02/21 10:08:11 UTC
[jira] [Resolved] (CAMEL-8378) Move Camel catalog commands to
separate module
[ https://issues.apache.org/jira/browse/CAMEL-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-8378.
--------------------------------
Resolution: Fixed
Assignee: Claus Ibsen
> Move Camel catalog commands to separate module
> ----------------------------------------------
>
> Key: CAMEL-8378
> URL: https://issues.apache.org/jira/browse/CAMEL-8378
> Project: Camel
> Issue Type: Task
> Components: karaf, tooling
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.15.0
>
>
> Today the catalog commands are part of the Camel karaf commands. We should move them to a separate module, so they dont clutter the existing karaf commands.
> Then the end user can install the camel-catalog feature in karaf if he/she wants to use the catalog commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)