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 2014/07/07 08:50:33 UTC

[jira] [Created] (KARAF-3102) "New" resolver leaves some bundles in resolved state

Jean-Baptiste Onofré created KARAF-3102:
-------------------------------------------

             Summary: "New" resolver leaves some bundles in resolved state
                 Key: KARAF-3102
                 URL: https://issues.apache.org/jira/browse/KARAF-3102
             Project: Karaf
          Issue Type: Bug
          Components: karaf-feature
    Affects Versions: 4.0.0
            Reporter: Jean-Baptiste Onofré
             Fix For: 4.0.0


It seems that the "new" bundle resolver leaves some bundles in resolved state (without any clear reason).

For instance, if we install the spring feature:

{code}
karaf@root()> feature:install spring
{code}

The aries util, aopalliance, ASM bundles stay in resolved state:

{code}
karaf@root()> la|grep -i resolved
 7 | Resolved |  30 | 2.12.0          | JLine                                                              
19 | Resolved |  20 | 1.1.0           | Apache Aries Util                                  
47 | Resolved |  20 | 5.0.3           | ASM all classes with debug info                                    
50 | Resolved |  30 | 1.0.0.6         | Apache ServiceMix :: Bundles :: aopalliance
{code}

These bundles are not fragment, and we start the bundle "by hand", they start without problem:

{code}
karaf@root()> bundle:start 50
karaf@root()> la|grep -i aopalliance
50 | Active   |  30 | 1.0.0.6         | Apache ServiceMix :: Bundles :: aopalliance
{code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)