Hi Konstantin, It's included as a dependency of the JAX-WS Tools component. Used in annotation validation code and tests.
It was bundled to prevent compiler errors being reported on the use of javax.xml.bind.* classes due to access restrictions as a result of the minimum BREE of all the bundles being set to J2SE-1.5. If you're unable to work around those wiring issues open a bugzilla against JAX-WS tools and I'll look to see what we can do to remove our dependency on the javax.xml.bind bundle without having to increase the BREE of the JAX-WS tools bundles. I'm not aware of anyone else having a dependency on it. Thanks, Shane From: konstantin.komissarc...@oracle.com To: wtp-dev@eclipse.org Date: Thu, 25 Sep 2014 11:43:37 -0700 Subject: [wtp-dev] Reason for javax.xml.bind bundle in WTP? We are seeing numerous OSGi wiring issues related to the javax.xml.bind package that started to crop up on Luna after Equinox changed wiring rules to not always prefer the version of the package that originates from the JDK. So my question is… Why is WTP including javax.xml.bind bundle, when the corresponding package is already exported by the platform from the JDK? Thanks, - Konstantin _______________________________________________ wtp-dev mailing list wtp-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list wtp-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
