[
https://issues.apache.org/jira/browse/KARAF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251530#comment-13251530
]
Anthony Masse edited comment on KARAF-1352 at 4/11/12 1:16 PM:
---------------------------------------------------------------
I believe that isn't an issue because the "Apache Karaf :: Cellar :: Hazelcast"
bundle is delacred as a "Fragment-Host" of the "hazelcast" bundle
See the MANIFEST.MF file
Fragment-Host: hazelcast
was (Author: amasse22):
I believe that isn't an issue because the "Apache Karaf :: Cellar ::
Hazelcast" bundle is delacred as a "Frament-Host" of the "hazelcast" bundle
See the MANIFEST.MF file
Fragment-Host: hazelcast
> "Apache Karaf :: Cellar :: Hazelcast" remains in "RESOLVED" state
> -----------------------------------------------------------------
>
> Key: KARAF-1352
> URL: https://issues.apache.org/jira/browse/KARAF-1352
> Project: Karaf
> Issue Type: Bug
> Components: cellar-hazelcast
> Affects Versions: 2.2.4
> Reporter: Alexandr Palto
> Priority: Minor
>
> After installation of cellar feature all bundles change own status to
> "ACTIVE" instead of Apache Karaf :: Cellar :: Hazelcast bundle. It remains
> with this OSGI status:
> karaf@trun> list
> START LEVEL 100 , List Threshold: 50
> ID State Blueprint Spring Level Name
> ............................................
> [ 213] [Resolved ] [ ] [ ] [ 80] Apache Karaf :: Cellar
> :: Hazelcast (2.2.4.SNAPSHOT)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
