[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Uses conflicts gone after "eclipse -clean":Why?
- From: Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>
- Date: Fri, 04 Apr 2014 17:30:33 +0200
- Delivered-to: email@example.com
- Organization: Codetrails
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
> Specifically the FrameworkWiring.refreshBundles() method can be used to
> force refresh and re-resolution of a subset of bundles.
thank you for the pointer.
But before I resort to this brute-force measure, I'd like to understand
the problem a bit better (never a bad idea ;-).
The uses conflict  happens if I first install feature A and then
(after the traditional restart) install feature B. After restarting
again some of A's bundles fail to resolve due to a uses conflict. (All
of B's bundles resolve just fine.)
>From what I have learned on this thread, if any bundle faces a uses
conflict then it should have been one of B's, as Equinox won't rewire
the already resolved bundles of A. But that's what seems to happen.
To make this even more mysterious for an OSGi novice like myself, -clean
causes all uses conflicts to go away.
I would be extremely grateful if someone could give me a hint as to what
part of OSGi bundle wiring I don't understand, as both feature A (Code
Recommenders) and B (m2e) are participating in the Luna release train
and we certainly don't want uses conflicts there.
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940