Yeah, the problem is the bundle constraints are limiting it to looking for < 2.0.0, so in other words 1.9.9 would be fine. We just need to up the bundle range as Andrew suggested. When you removed the jclouds.osgi.fragment property, it defaulted to finding the highest available version which is why it worked.
-Chris -- Chris Custine On August 15, 2014 at 2:59:46 PM, Andrew Phillips (aphill...@qrmedia.com) wrote: > > I did not see the “jclouds.osgi.fragment” configured in any other > > poms, so I removed it and all of the Karaf tests pass now. ?? > > A bit of a shot in the dark, but could you try with > > jclouds-core;bundle-version="[1.3,3)" > > ? I wonder whether it was refusing to load jclouds-core now that we're > up to 2.0.0-SNAPSHOT... > > ap >
