I didn’t much like my solution either. Fortunately we were able to modify the
bundle that introduced the use of javax.annotation: the javax.annotation import
was a compile-time dependency, not a runtime dependency. So all is now well.
Thanks for your feedback!
Brian.
> On 20-Jun-2016, at 3:3
Yes it’s a very common misconception that the Framework always chooses the
highest version it can find — I have to address this in every training course I
run.
It *may* prefer the highest version if everything else about the resulting
outcomes is equal. But that is an unrealistic assumption, an
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
