|[wtp-dev] Behavior change notice for OSGi bundles libraries provider|
This is a notice of minor last-minute change made for 3.1 RC2 in the OSGi bundles libraries provider (part of the libraries provider framework that is new for 3.1). The classpath container in question was originally written to contribute to the system boot classpath. This proved problematic for some EclipseLink use cases and the container needed to be changed to contribute to application classpath instead.
See this bug for more information:
If there are adopters of this technology who think that they depend on the system boot classpath behavior of this feature, please comment on the bug and we will find a solution that works for everyone.
Back to the top