-
New Feature
-
Resolution: Won't Fix
-
Minor
As discussed in JENKINS-51821, Jenkins won't work on Java 11 due to removed JAXB modules. I propose the following approach:
- Package 3 JAXB libs (jaxb-api-2.3.0.jar, jaxb-core-2.3.0.1.jar, jaxb-impl-2.3.0.1.jar) to a WAR resource which does not get classloaded by default. E.g. "WEB-INF/platform-compat/java11" (or 9 ?)
- When Jenkins starts up on Java 9+, Jenkins WAR exploder copies the libraries to "war/WEB-INF/lib" so that they get picked by classloader automatically
It will allow to have a transparent support of Java 9..11 within the WAR file (without adding modules, etc.)
A better way forward would be Multi-Version JAR, but we need a massive tooling update to support it
- blocks
-
JENKINS-52186 Java 11: Upstream the JAXB bundling to the master branch
-
- Closed
-
- causes
-
JENKINS-55944 Remove JAXB dependencies for better Java 11 readiness
-
- Closed
-
- relates to
-
JENKINS-55620 SloccountPublisher fails on Java 11 without --add-modules java.xml.bind
-
- Resolved
-
-
JENKINS-46600 [JDK 9] Jenkins does not start with "java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter"
-
- Resolved
-
-
JENKINS-53938 Warnings plugin 'Record static analysis results - GNU Make + GNU C Compiler (gcc)’ gives exception with Java 10
-
- Resolved
-
-
JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11
-
- Closed
-
-
JENKINS-51821 Explore impact of Java EE removal in Jenkins Core with Java 11
-
- Resolved
-
-
JENKINS-55572 Remove JAXB usages in codesonar plugin for Java 11 compatibility
-
- Resolved
-
-
JENKINS-55704 Run jenkinsci/usage-in-plugins on JAXB usages
-
- Closed
-
-
JENKINS-52004 Add java.activation module to Java 10 Docker packages
-
- Resolved
-
-
JENKINS-55681 Release the JAXB Plugin
-
- Resolved
-
- links to
[JENKINS-51965] Add support of JAXB unpackaging for Java 9+ in WAR Exploder
Epic Link |
New:
|
Labels | New: java10_hackathon |
Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
Link |
New:
This issue relates to |
Link |
New:
This issue relates to |
Description |
Original:
As discussed in JANNKINS-51821, Jenkins won't work on Java 11 due to removed JAXB modules. I propose the following approach: * Package 3 JAXB libs (jaxb-api-2.3.0.jar, jaxb-core-2.3.0.1.jar, jaxb-impl-2.3.0.1.jar) to a WAR resource which does not get classloaded by default. E.g. "WEB-INF/platform-compat/java11" (or 9 ?) * When Jenkins starts up on Java 9+, Jenkins WAR exploder copies the libraries to "war/WEB-INF/lib" so that they get picked by classloader automatically It will allow to have a transparent support of Java 9..11 within the WAR file (without adding modules, etc.) A better way forward would be Multi-Version JAR, but we need a massive tooling update to support it |
New:
As discussed in * Package 3 JAXB libs (jaxb-api-2.3.0.jar, jaxb-core-2.3.0.1.jar, jaxb-impl-2.3.0.1.jar) to a WAR resource which does not get classloaded by default. E.g. "WEB-INF/platform-compat/java11" (or 9 ?) * When Jenkins starts up on Java 9+, Jenkins WAR exploder copies the libraries to "war/WEB-INF/lib" so that they get picked by classloader automatically It will allow to have a transparent support of Java 9..11 within the WAR file (without adding modules, etc.) A better way forward would be Multi-Version JAR, but we need a massive tooling update to support it |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Assignee | New: Kohsuke Kawaguchi [ kohsuke ] |
Remote Link | New: This issue links to "https://github.com/jenkinsci/jenkins/pull/3510 (Web Link)" [ 20945 ] |