You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/02/09 18:50:35 UTC

[jira] [Updated] (KARAF-3468) Command extender should bring up commands individually as their dependencies are available

     [ https://issues.apache.org/jira/browse/KARAF-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-3468:
----------------------------------------
    Fix Version/s:     (was: 4.0.0.M2)

> Command extender should bring up commands individually as their dependencies are available
> ------------------------------------------------------------------------------------------
>
>                 Key: KARAF-3468
>                 URL: https://issues.apache.org/jira/browse/KARAF-3468
>             Project: Karaf
>          Issue Type: Improvement
>    Affects Versions: 4.0.0.M1
>            Reporter: Christian Schneider
>             Fix For: 4.0.0
>
>
> Currently the Command extender only starts commands a bundle provides together. It waits till all services required by all commands are there and then start all commands together.
> I have a case in config.core where I would like to create a command that shows meta type informations. The other commands only depend on the config admin service and so should come up early.  The config:meta command should only come up when the MetaTypeService is installed but it should not prevent the other commands from coming up like it is the case now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)