Thanks for response. The nasty aspect of this issue is that it isn't a single problem. So far we have seen three different manifestations, but many more likely exist since a slightly different install or p2 resolve order will bring another occurrence. Sometimes, you can work-around these problems by restarting eclipse with -clean switch. Of course, users aren't going to know to do this. Many users don't even know to check the error log. All they see is that some plugins are "missing" (aka not activated) once Eclipse starts.
We will keep investigating and update on this thread with what we find. For now, one question. Is there a specific documented adopter requirement for keeping WTP bundles at Java 5 level? I notice the Eclipse IDE for Java EE developers has been requiring Java 6 since Kepler. Thanks, - Konstantin From: [email protected] [mailto:[email protected]] On Behalf Of Shane Clarke Sent: Monday, September 29, 2014 3:22 AM To: General discussion of project-wide or architectural issues. Subject: Re: [wtp-dev] Reason for javax.xml.bind bundle in WTP? 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: [email protected] To: [email protected] 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 [email protected] 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 [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
