[
https://issues.apache.org/jira/browse/KARAF-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322770#comment-14322770
]
Guillaume Nodet commented on KARAF-3468:
----------------------------------------
Two remarks:
* i'd like to keep the command extender as simple as possible and definitely
not turn it into an SCR like implementation
* I understand the fact that commands may depend on different services,
however does it really make sense to display meta information if the meta
service is not available ? Also, when the feature will be installed , won't it
actually install the service ? If so, the use case is pretty thin...
> 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)
