Hello!

A few months back, I was looking into using the resolver outside of an
OSGi context. What I wanted to do was call a resolver with a set of
requirements, and have it tell me the set of bundles I need to
retrieve in order to start up an OSGi framework with everything
required installed.

I came up with this:

  
https://github.com/io7m/resolver-test-20180322/blob/master/src/main/java/com/io7m/felixresolver/Main.java

Now, this works for these silly example bundles. The problem is that
real bundles contain requirements such as:

  osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=9.0))"

These will obviously fail given the resolver context in the example
program because it doesn't contain any of the capabilities that a real
framework would provide. What is the correct way to deal with this? I'm
not sure I should be inserting fake capabilities myself (it's not
entirely clear how I could even do this), and I'm not sure I could
filter requirements without prior knowledge of each and every
requirement.

-- 
Mark Raynsford | http://www.io7m.com

Attachment: pgpQv3cV1bEmP.pgp
Description: OpenPGP digital signature

Reply via email to