[KARAF-3102] "New" resolver leaves some bundles in resolved state and install unexpected bundles

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.0.M3
• Fix Version/s: 4.0.0.M3
• Component/s: karaf
• Assignee: Christian Schneider
• Reporter: Jean-Baptiste Onofré
• Created: 07/Jul/14 06:49
• Updated: 14/Sep/18 15:14
• Resolved: 13/Apr/15 12:12

Description

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:

karaf@root()> feature:install spring

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

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

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

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