[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 14:45:16 +0200
- Delivered-to: firstname.lastname@example.org
- Organization: Codetrails
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
> 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.
is there a way to force a rewiring upon an install of a bundle/feature?
We have a very nasty bundle upgrade problem that runs into uses
conflicts as another bundle (org.eclipse.m2e.maven.runtime)
overzealously claims that it exports version 0.0.0 of many, many
packages, some of which we require in a specific, different version.
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940