Hi Alan,
It might be easier to build bundles yourself for some of these dependencies. That will give you a bit more fine-grained control over which packages are private, exported and imported from the different bundles. Some of the imports can probably also be marked optional as well, thus reducing the number of bundles and dependencies you have to "OSGi-fy". You can have a look at the sources under http://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/ to see how we build ours for Apache ServiceMix. Some of the bundles you're looking for are probably already there (paranamer, scala-library, casbah) so you might be able to find some inspiration there. Also, for liftweb, it may be easier to build a single bundle that contains the different liftweb modules (similar to e.g. how our drools 5.5.0 bundle is built). I notice some of these dependencies do have compatible licenses (BSD, Apache v2), so if you have something working, we would definitely welcome a patch with the bundle pom.xml you created ;) Regards, Gert Vanthienen On Thu, Apr 18, 2013 at 7:03 PM, alanfoster <a...@alanfoster.me> wrote: > Hi Willem, > > Thanks for the response > > When I first tried to install my bundle it did firstly complain about > mongodb. > > I started adding the dependencies it asked for to my feature files one by > one. I eventually ended up with these bundles added to my servicemix > features file > > <bundle>mvn:org.mongodb/mongo-java-driver/2.9.3</bundle> > > <bundle>mvn:ch.qos.logback/logback-core/0.9.27</bundle> > <bundle>mvn:ch.qos.logback/logback-classic/0.9.27</bundle> > > <bundle>mvn:net.liftweb/lift-common_2.9.1/2.4-M5</bundle> > > <bundle>mvn:net.liftweb/lift-actor_2.9.1/2.4-M5</bundle> > <bundle>wrap:mvn:com.thoughtworks.paranamer/paranamer/2.3</bundle> > > <bundle>wrap:mvn:org.scala-lang/scalap/2.9.1</bundle> > > <bundle>mvn:net.liftweb/lift-json_2.9.1/2.4-M5</bundle> > <bundle>mvn:net.liftweb/lift-util_2.9.1/2.4-M5</bundle> > > <bundle>mvn:net.liftweb/lift-webkit_2.9.1/2.4-M5</bundle> > > <bundle>mvn:net.liftweb/lift-mongodb-record_2.9.1/2.4-M5</bundle> > > <bundle>wrap:mvn:com.foursquare/rogue-lift_2.9.1/2.0.0-RC1</bundle> > > But I just keep getting dependency issues one after another > > This is the latest dependency issue I am getting. But they just seem to go > on one after another... > > Error executing command: Could not start bundle > mvn:net.liftweb/lift-json_2.9.1/2.4-M5 in feature(s) scala-test-0.0.0: > Unresolved constraint in bundle net.liftweb.lift.json [266]: Unable to > resolve 266.0: missing requirement [266.0] osgi.wiring.package; > (&(osgi.wiring.package=scala.tools.scalap.scalax.rules.scalasig)(version>=2.9.1)(version<=2.9.1)) > > For reference I did an osgi:headers on my bundle, and I can see most of the > dependencies are from net liftweb > > Import-Package = > com.mongodb;version="[2.9,3)", > net.liftweb.common;version="[2.4,3)", > net.liftweb.http;version="[2.4,3)", > net.liftweb.http.js;version="[2.4,3)", > net.liftweb.json;version="[2.4,3)", > net.liftweb.mongodb;version="[2.4,3)", > net.liftweb.mongodb.record;version="[2.4,3)", > net.liftweb.record;version="[2.4,3)", > net.liftweb.record.field;version="[2.4,3)", > net.liftweb.util;version="[2.4,3)", > org.apache.camel;version="[2.10,3)", > org.bson.types;version="[2.9,3)", > org.osgi.service.blueprint;version="[1.0.0,2.0.0)", > scala, > scala.collection, > scala.collection.immutable, > scala.reflect, > scala.runtime, > scala.xml > > Am I doing something wrong? Is there any other way to resolve my > dependencies? > > Thanks > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/Resolving-Scala-Osgi-Dependencies-tp5716520p5716562.html > Sent from the ServiceMix - User mailing list archive at Nabble.com.
