Nice idea Chris, you'll then be the only one that will be able to understand felix dependency error messages
2014-12-18 13:34 GMT+01:00 <[email protected]>: > > In any case Milan is misinterpreting the message. Felix is saying that it > could not find a provider for the package my.package.api with version >= > 1.0.0 but not >= 2.0.0; in other words he "expects" 1.x.x and he "found" > nothing that matches his expectations. I have to admit that LDAP syntax is > not ideally matched to the human brain, maybe OSGi should switch to using > FORTH? Something like: > > osgi.wiring.package dup dup my.package.api = 1.0.0 >= 2.0.0 < and and > > ;-) > > > > Hi, > > > > That message is from Apache Felix but not Karaf. > > > > You may need post request there. > > －－－－－－－－－－－－－ > > Freeman(Yue) Fang > > > > Red Hat, Inc. > > FuseSource is now part of Red Hat > > > > > > > > On 2014-12-18, at 下午7:38, Milan Tomic wrote: > > > >> Hi, > >> > >> If you could please change error message from: > >> > >> Unable to resolve 140.0: missing requirement [140.0] > >> osgi.wiring.package; > >> > (&(osgi.wiring.package=my.package.api)(version>=1.0.0)(!(version>=2.0.0))) > >> > >> to: > >> > >> Unable to resolve 140.0: missing requirement [140.0] > >> osgi.wiring.package; (&(osgi.wiring.package=my.package.api)(found: > >> version>=1.0.0)(!(expected: version>=2.0.0))) > >> > >> (I added "found" and "expected") > >> > >> because it is not intuitive and each time I got this error message I > >> have to search for its meaning. > >> > >> Thank you, > >> Milan > > > > > > > -- Charlie Mordant Full OSGI/EE stack made with Karaf: https://github.com/OsgiliathEnterprise/net.osgiliath.parent
