[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Uses conflicts gone after "eclipse -clean":Why?

I'm reminded of an old joke. A tourist is lost in Ireland, so he stops his rental car and asks a nearby farmer, how can I get to Dublin from here? The farmer's reply: "Dublin?? Oh, you can't get there from here!"

The point is that in OSGi, resolution proceeds from the current wiring state, and sometimes a set of bundles would fail with a uses-constraint violation if installed on the top of the current wiring state. However if you're prepared to break apart and rewire the existing state, then a solution can often be found.


On Fri, Mar 21, 2014 at 5:27 PM, Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx> wrote:
Hi all,

Pardon me if this is the wrong mailing list for this question, but as
there doesn't seem to be a dedicated equinox-users list, I hope you
don't mind if I ask here.

I have two features (one third-party, one of our own). If I install
first one of them into a fresh Eclipse (Luna M6, to be precise) and then
the other, some bundles from our own feature fail to resolve with a uses
conflict. The same thing happens if I change the order of installation
(but oddly enough not when I install both bundles at the same time.)

This uses conflict is resolvable, however. If I start Eclipse with
"-clean" it comes up with a perfectly fine solution that wires all the
bundles together without a uses conflict.

So here's my question: Is this a bug or simply a misconception of mine
about how Equinox performs its uses constraint solving? I would assume
that if a solution exists, which "-clean" does find, than it would also
get picked after an install.

Best wishes,


Codetrails UG (haftungsbeschrÃnkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
equinox-dev mailing list