BTW regarding that resolution error… the OSGi Compendium JAR does now have “must.not.resolve” because it is not appropriate for runtime usage. But you can use any of the APIs from the compendium by downloading the individual spec bundle for that API. For example, the HttpService spec JAR is here:
http://search.maven.org/#artifactdetails|org.osgi|org.osgi.service.http|1.2.1|jar Neil On Thu, Oct 1, 2015 at 4:24 PM, Carsten Ziegeler <cziege...@apache.org> wrote: > Yes, you're right ,the docs are outdated :( > (I'll try to update them) > > Carsten > > Am 01.10.15 um 16:54 schrieb Thomas Driessen: > > That worked! Thanks a lot. > > > > Might it be, that the documentation for the felix.http project is a > little > > bit outdated? ( > > > http://felix.apache.org/documentation/subprojects/apache-felix-http-service.html > ). > > Or am I just searching at the wrong place? > > > > Kind regards, > > Thomas > > > > 2015-10-01 16:39 GMT+02:00 Carsten Ziegeler <cziege...@apache.org>: > > > >> I think you're missing the org.apache.felix.http.api bundle, version > 3.0.0 > >> > >> Carsten > >> > >> Am 01.10.15 um 13:12 schrieb Thomas Driessen: > >>> Hi, > >>> > >>> I just started with a fresh Installation of Eclipse and BndTools > 3.0.0. I > >>> tried to run a minimal setup with: > >>> > >>> -runrequires: \ > >>> osgi.identity;filter:='(osgi.identity=org.apache.felix.gogo.shell)',\ > >>> osgi.identity;filter:='(osgi.identity=org.apache.felix.gogo.command)',\ > >>> osgi.identity;filter:='(osgi.identity=TexoTest)',\ > >>> > >> > osgi.identity;filter:='(&(osgi.identity=org.apache.felix.http.jetty)(version>=3.1.0))' > >>> > >>> where "TexoTest" is my own bundle and ended up with the following error > >>> when resolving the bundles: > >>> > >>> org.osgi.service.resolver.ResolutionException: Unable to resolve > >>> <<INITIAL>> version=null: missing requirement > >> org.apache.felix.http.jetty; > >>> version=3.1.0 > >>> -> Unable to resolve org.apache.felix.http.jetty version=3.1.0: > missing > >>> requirement org.osgi.service.http.context; version=[1.0.0,1.1.0) > >>> -> Unable to resolve osgi.cmpn version=6.0.0.201505202027: missing > >>> requirement &(must.not.resolve=*)(must.not.resolve!=*)]] > >>> > >>> Is this an intended behaviour? As of v 6.0.0 the cpmn bundle has this > >>> "must.not.resolve" thing. So do I get it right and I have to wait for > >>> org.osgi.service.http.context to be updated so that the cpmn is not a > >>> mandatory dependency for it anymore? > >>> > >>> Best regards, > >>> Thomas > >>> > >> > >> > >> -- > >> Carsten Ziegeler > >> Adobe Research Switzerland > >> cziege...@apache.org > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > >> For additional commands, e-mail: users-h...@felix.apache.org > >> > >> > > > > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > For additional commands, e-mail: users-h...@felix.apache.org > >
