[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [equinox-dev] Force particular bundle wirings to deal with split packages?
|
| 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 …
Kind regards,
Peter Kriens
On 17-Jun-2016, at 1:08 PM, Neil Bartlett < njbartlett@xxxxxxxxx> wrote: 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.
Brian. _______________________________________________ equinox-dev mailing list equinox-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
