Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
framework-4.0.0
-
None
Description
Singleton bundle selection happens at the beginning of each resolve operation, at which point the highest version singleton is selected for each symbolic name grouping and the associated capabilities are indexed and made available in the resolver state. This works correctly when all bundles are unresolved; however, there is a bug when a singleton is resolved before a dependent bundle. In that case, the resolved singleton's capabilities are de-indexed and are never indexed again. The capabilities for a resolved singleton should not be de-indexed, since it has been selected and its capabilities should be available.