Hello,
That is interesting and tools and visualizations to help in this area
are certainly needed. However, depending on your OSGi framework you can
get a pretty precise description of a uses constraint violation. For
example, both the Felix framework and Equinox use the same resolver
which spits out a pretty detailed textual "graph" showing you how the
uses constraint violation occurred. So, following the documented steps
and learning SPARQL to get the same information is probably a little too
much effort.
Still, it is interesting to be able to visualize this stuff. Perhaps you
should look into instrumenting the Felix resolver so you can create your
visualizations for a given failed resolve permutation, rather than
having to use your "back off" approach.
-> richard
On 8/11/15 09:45 , Lurie, Aron wrote:
Hi All,
I've made a contribution to the literature on resolving OSGi uses
constraint violations and I would like to bring it to your attention
and open it up for discussion here.
http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo
<http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo>
Resolving OSGi "Uses Constraint Violations" Using Anzo
Technical, ANZO, Advanced
Read more...
<http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo>
Thanks,
Aron
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
