[cross-project-issues-dev] Java 11 (OpenJDK 11): javax.xml.bind package removed

[Keith Chong]

Are other teams affected by the removal of the javax.xml.bind package from
Java 11?

Web Tools Platform (WTP) Web services has 'unresolved' references when
running with Java 11. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=539771.

The solution would simply be to pull the javax.xml.bind package into WTP
(from orbit), but, it was originally pulled out of WTP because of
https://bugs.eclipse.org/bugs/show_bug.cgi?id=446080
due to OSGi wiring issues. If we proceed with this solution, we might
re-introduce the wiring issues when using a Java level (non-Java 11) that
contains the deprecated packages.

The info in the two bugzillas indicate that other teams might be impacted
by this. Dali (eg. eclipselink packages) and MyLyn. Thoughts?

Regards,
Keith Chong
WTP Web Services

[Roland Grunberg]

Are other teams affected by the removal of the javax.xml.bind package from Java 11?
Web Tools Platform (WTP) Web services has 'unresolved' references when running with Java 11. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=539771.
The solution would simply be to pull the javax.xml.bind package into WTP (from orbit), but, it was originally pulled out of WTP because of https://bugs.eclipse.org/bugs/show_bug.cgi?id=446080
due to OSGi wiring issues. If we proceed with this solution, we might re-introduce the wiring issues when using a Java level (non-Java 11) that contains the deprecated packages.
The info in the two bugzillas indicate that other teams might be impacted by this. Dali (eg. eclipselink packages) and MyLyn. Thoughts?

Orbit is affected by this in the sense that there are packages that
depend on javax.xml.bind (versionless) that we ship. In
http://eclip.se/539515 I've converted all the ones shipped in orbit-
recipes (this is in our M1 contribution) so they'll resolve against our
javax.xml.bind bundle but there's still a few more to fix.

Cheers,

[Tom Schindl]

Hi,

e(fx)clipse is affected by this as well but the bundle in Orbit quite
old. It's been on my list to bring the the latest javax.xml.bind version
to orbit.

Tom

Post by Roland Grunberg

Are other teams affected by the removal of the javax.xml.bind package from Java 11?
Web Tools Platform (WTP) Web services has 'unresolved' references when running with Java 11. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=539771.
The solution would simply be to pull the javax.xml.bind package into WTP (from orbit), but, it was originally pulled out of WTP because of https://bugs.eclipse.org/bugs/show_bug.cgi?id=446080
due to OSGi wiring issues. If we proceed with this solution, we might re-introduce the wiring issues when using a Java level (non-Java 11) that contains the deprecated packages.
The info in the two bugzillas indicate that other teams might be impacted by this. Dali (eg. eclipselink packages) and MyLyn. Thoughts?

Orbit is affected by this in the sense that there are packages that
depend on javax.xml.bind (versionless) that we ship. In
http://eclip.se/539515 I've converted all the ones shipped in orbit-
recipes (this is in our M1 contribution) so they'll resolve against our
javax.xml.bind bundle but there's still a few more to fix.
Cheers,