[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Uses conflicts gone after "eclipse -clean":Why?
- From: Thomas Watson <tjwatson@xxxxxxxxxx>
- Date: Mon, 24 Mar 2014 13:30:53 -0500
- Delivered-to: email@example.com
Neil's response is accurate. The issue is that we have made some prior wiring decisions that cannot be changes later for already resolved bundles. Using -clean allows us to wipe all previous decisions away and start fresh which then can allow us for freedom in the decisions with respect to obtaining a consistent class space.
Andreas Sewe ---03/21/2014 12:27:41 PM---Hi all, Pardon me if this is the wrong mailing list for this question, but as
From: Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>
Date: 03/21/2014 12:27 PM
Subject: [equinox-dev] Uses conflicts gone after "eclipse -clean":Why?
Sent by: equinox-dev-bounces@xxxxxxxxxxx
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.
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
equinox-dev mailing list