Hi Yes, the idea is always the same: don't deploy the compendium API bundle. This will break your deployment sooner or later. The compeniumd bundle exposes API versions which may not reflect the actual API versions provided and/or used in your setup.
Regards Felix Am 05.06.2013 um 05:52 schrieb Martin Lichtin: Hi Ariès I am wondering what the preferred way is to avoid the "not compatible with this blueprint extender" issue. But two steps back first: The issue started popping up after using org.osgi.compendium/4.3.1 (as deemed appropriate for Karaf 2.3.1). (compendium bundle is needed because of the H2 bundle recently starting to require "org.osgi.service.jdbc"). -> both org.osgi.compendium/4.3.1 and org.apache.aries.blueprint.api/1.0.0 export the BlueprintContainer interface. When Aries scans a bundle for BP, it checks that the bundle classloader picks up the Aries BlueprintContainer class. If not, it spits out above mentioned "is not compatible" info message. So far, so good. However, I have some bundles that need "DynamicImport-Package=*". Their classloader unfortunately loads the BlueprintContainer interface from org.osgi.compendium. Any ideas how I can configure my bundle so it prefers the Aries bundle for loading "BlueprintContainer.class"? Martin
