Hi again,

it seems I got a little bit confused. I didn't mean
"org.osgi.service.http.context" to get updated, but
"org.apache.felix.http.jetty". The first one is only the exported package
felix.http.jetty has a dependency on, as I understand it.

Kind regards,
Thomas

2015-10-01 13:12 GMT+02:00 Thomas Driessen <thomas.driessen...@gmail.com>:

> 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
>

Reply via email to