You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Alexandr Palto (Created) (JIRA)" <ji...@apache.org> on 2012/04/11 14:28:16 UTC
[jira] [Created] (KARAF-1352) "Apache Karaf :: Cellar :: Hazelcast"
remains in "RESOLVED" state
"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 status:
[ 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
[jira] [Updated] (KARAF-1352) "Apache Karaf :: Cellar :: Hazelcast"
remains in "RESOLVED" state
Posted by "Alexandr Palto (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandr Palto updated KARAF-1352:
----------------------------------
Description:
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)
was:
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:
[ 213] [Resolved ] [ ] [ ] [ 80] Apache Karaf :: Cellar :: Hazelcast (2.2.4.SNAPSHOT)
> "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
[jira] [Commented] (KARAF-1352) "Apache Karaf :: Cellar ::
Hazelcast" remains in "RESOLVED" state
Posted by "Anthony Masse (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251530#comment-13251530 ]
Anthony Masse commented on KARAF-1352:
--------------------------------------
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
[jira] [Commented] (KARAF-1352) "Apache Karaf :: Cellar ::
Hazelcast" remains in "RESOLVED" state
Posted by "Jean-Baptiste Onofré (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251857#comment-13251857 ]
Jean-Baptiste Onofré commented on KARAF-1352:
---------------------------------------------
It's normal, Cellar Hazelcast is a fragment of the hazelcast bundle.
> "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: cellar-2.2.4
> Reporter: Alexandr Palto
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> 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
[jira] [Issue Comment Edited] (KARAF-1352) "Apache Karaf :: Cellar
:: Hazelcast" remains in "RESOLVED" state
Posted by "Anthony Masse (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (KARAF-1352) "Apache Karaf :: Cellar :: Hazelcast"
remains in "RESOLVED" state
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-1352:
----------------------------------------
Affects Version/s: (was: 2.2.4)
cellar-2.2.4
Fix Version/s: cellar-2.2.4
cellar-3.0.0
Assignee: Jean-Baptiste Onofré
> "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: cellar-2.2.4
> Reporter: Alexandr Palto
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> 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
[jira] [Resolved] (KARAF-1352) "Apache Karaf :: Cellar ::
Hazelcast" remains in "RESOLVED" state
Posted by "Jean-Baptiste Onofré (Resolved JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-1352.
-----------------------------------------
Resolution: Not A Problem
> "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: cellar-2.2.4
> Reporter: Alexandr Palto
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> 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
[jira] [Updated] (KARAF-1352) "Apache Karaf :: Cellar :: Hazelcast"
remains in "RESOLVED" state
Posted by "Alexandr Palto (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandr Palto updated KARAF-1352:
----------------------------------
Description:
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:
[ 213] [Resolved ] [ ] [ ] [ 80] Apache Karaf :: Cellar :: Hazelcast (2.2.4.SNAPSHOT)
was:
After installation of cellar feature all bundles change own status to "ACTIVE" instead of Apache Karaf :: Cellar :: Hazelcast bundle. It remains with this status:
[ 213] [Resolved ] [ ] [ ] [ 80] Apache Karaf :: Cellar :: Hazelcast (2.2.4.SNAPSHOT)
> "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:
> [ 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
[jira] [Issue Comment Edited] (KARAF-1352) "Apache Karaf :: Cellar
:: Hazelcast" remains in "RESOLVED" state
Posted by "Anthony Masse (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ 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:17 PM:
---------------------------------------------------------------
I believe that it 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 "Fragment-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