[
https://issues.apache.org/jira/browse/KARAF-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606952#comment-13606952
]
Achim Nierbeck commented on KARAF-1249:
---------------------------------------
realized that the fragmentation of hazelcast and cellar feature is not enough
after starting, since due to the fact that the features resolver doesn't really
care about the startlevels between two features the hazelcast fails to retrieve
classes from core.
So I seperated cellar core (including the config files) from the main cellar
feature. First step of a finer grained features xml.
This way cellar installs more friendly
> Provide more fine grained Cellar features
> -----------------------------------------
>
> Key: KARAF-1249
> URL: https://issues.apache.org/jira/browse/KARAF-1249
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-core
> Affects Versions: cellar-2.2.3
> Reporter: Jean-Baptiste Onofré
> Assignee: Achim Nierbeck
> Fix For: cellar-3.0.0, cellar-2.3.0
>
>
> Currently, the cellar feature installs all cellar bundles (core, commands,
> mbeans, etc).
> More over, all is in the same bundle (aka for install the cluster:features-*
> commands, mbeans, events, etc are in the same bundles).
> It means that the users are not able to choose exactly what they want to
> install. For instance, in a central managed configuration, the managed nodes
> should not provide the cluster:* commands.
> I will refactore Cellar to "explode" it in different atomic bundles and
> provide fine grained cellar features.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
