Ah, I was surprised by Richard’s comment as well. We’ve been using equinox for a while and never had a nice “uses constraint violation” message, which meant lots of time debugging those. In fact, the first answer that Peter K. gave me on Stackoverflow about these problems was “use felix to troubleshoot”
But this explains it, we are using equinox 3.9. But it’s good to know about this new feature in equinox From: osgi-dev-boun...@mail.osgi.org [mailto:osgi-dev-boun...@mail.osgi.org] On Behalf Of Thomas Watson Sent: Tuesday, August 11, 2015 12:30 PM To: osgi-dev@mail.osgi.org Subject: Re: [osgi-dev] Resolving OSGi "Uses Constraint Violations" UsingAnzo For Equinox, it depends on what version you are using. The Luna release (Equinox framework version 3.10.x) is the first to use the same resolver implementation as felix and should provide the same level of error messages for uses constraint violations. Prior to Luna the error messages would not very helpful for uses constraint violations. Tom ----- Original message ----- From: "Lurie, Aron" <a.lu...@wustl.edu<mailto:a.lu...@wustl.edu>> Sent by: osgi-dev-boun...@mail.osgi.org<mailto:osgi-dev-boun...@mail.osgi.org> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org>> Cc: Subject: Re: [osgi-dev] Resolving OSGi "Uses Constraint Violations" Using Anzo Date: Tue, Aug 11, 2015 11:04 AM Hi Richard, Thanks for your comments, you make some good suggestions. One way to create visualizations for a failed resolve might be to have the resolver generate the relevant RDF, and load that into a server that resolved (and thus runs the visualization tool). Can you point me to an example of what Equinox or Felix provides in terms of uses constraint violation information? I use Equinox primarily, and my experience was that only a small amount of high level information (the bundle that couldn't be resolved, and the package with the uses constraint) was provided regarding the cause of the violation. It didn't point out which uses constraint was violated. Thanks, Aron ________________________________ From: osgi-dev-boun...@mail.osgi.org<mailto:osgi-dev-boun...@mail.osgi.org> <osgi-dev-boun...@mail.osgi.org<mailto:osgi-dev-boun...@mail.osgi.org>> on behalf of Richard S. Hall <he...@ungoverned.org<mailto:he...@ungoverned.org>> Sent: Tuesday, August 11, 2015 9:30 AM To: OSGi Developer Mail List Subject: Re: [osgi-dev] Resolving OSGi "Uses Constraint Violations" Using Anzo 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<http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo> Technical, ANZO, Advanced<http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo> Read more...<http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo> Thanks, Aron <http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo> <http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo> _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev<http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo> _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev<http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo> <http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo> DISCLAIMER: Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
