Thanks Achim. I believe 1.0.1.M01 of gemini blueprint fixes this by specifying version ranges [3.0.0, 4.0).
-tony On Wed, Jun 20, 2012 at 4:48 PM, Achim Nierbeck <[email protected]>wrote: > Just one side note :) > > afaik gemini 1.0 doesn't support Spring 3.1.1, you probably need also > need a never version of gemini. > > regards, Achim > > 2012/6/20 Anthony Bargnesi <[email protected]>: > > Hi guys, > > > > I'm familiar with the work done in KARAF-928 > > (https://issues.apache.org/jira/browse/KARAF-928) > > to support gemini-blueprint as a feature, however it is targeted for > > 3.0.0-SNAPSHOT. > > > > I'm looking to run spring 3.1.1 + gemini blueprint 1.0.0 in karaf 2.2.7. > > > > I have tried installing the gemini-blueprint feature using 3.0.0-SNAPSHOT > > and received NoSuchFieldError stacktraces. > > Attached as exception3.0.0.log. > > > > If I use the spring 3.1.1 / gemini blueprint features from > 3.0.0-SNAPSHOT in > > 2.2.7 I have a wiring > > problem: > > > > karaf@root> feature:install gemini-blueprint > > Error executing command: Could not start bundle > > > mvn:org.apache.karaf.deployer/org.apache.karaf.deployer.spring/3.0.0-SNAPSHOT > > in feature(s) spring-3.1.1.RELEASE: Unresolved constraint in bundle > > org.apache.karaf.deployer.spring [70]: Unable to resolve 70.0: missing > > requirement [70.0] package; > > (&(package=org.osgi.framework)(version>=1.6.0)(!(version>=2.0.0))) > > > > What would the best course of action be? > > > > Thanks, > > Anthony Bargnesi > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> > Committer & Project Lead > OPS4J Pax for Vaadin > <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project > Lead > blog <http://notizblog.nierbeck.de/> >
