[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Force particular bundle wirings to deal with split packages?
- From: Peter Kriens <peter.kriens@xxxxxxxxx>
- Date: Mon, 20 Jun 2016 09:18:21 +0200
- Delivered-to: email@example.com
|Note that a version bump does not guarantee that it will be the provider of the package. The framework can heuristics to do this but these are not specified to allow optimizations we could not foresee.|
Another idea to use is to put the messed up packages on the frameworkâs classpath. This will export them from the framework side. Since these are resolved from the start and the uses constraints match the framework it is extremely unlikely they are not picked.
Youâre in a nice mess â
On 17-Jun-2016, at 1:08 PM, Neil Bartlett <njbartlett@xxxxxxxxx
If youâre unable to change the bundles then no, not really. The only way is to not install these bundles that have exports of javax.annoation.
I ended up following the process we used with hollowing out javax.annotation: making a bundle that:
- includes the other bundles as jars
- âRequire-Bundle: system.bundleâ to pull in the JVMâs javax.annotation classes
- Import-Package of the various javax.annotation packages in the bundled jars in case theyâre already around
- Export-Package of the various javax.annotation packages in the bundled jars with a micro version bump to beat any of the existing jars.
That seems to work.
equinox-dev mailing listequinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Description: S/MIME cryptographic signature