-
Improvement
-
Resolution: Won't Do
-
Minor
Currently we have the module enabled automatically only for Java 11.
duemir recently reported that it was needed to Run on his instance, so it would worth to add the module to Java 10 packaging as well.
The following file should be patched: https://github.com/jenkinsci/docker/blob/java10/jenkins.sh
- relates to
-
JENKINS-51965 Add support of JAXB unpackaging for Java 9+ in WAR Exploder
-
- Closed
-
[JENKINS-52004] Add java.activation module to Java 10 Docker packages
Epic Link |
New:
|
Labels | New: java10_hackathon newbie-friendly |
Attachment | New: java.xml.bind.desc [ 43006 ] |
Link |
New:
This issue relates to |
Resolution | New: Won't Do [ 10001 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Labels | Original: java10_hackathon newbie-friendly | New: java10_hackathon java11 newbie-friendly |
I ran:
$JAVA10_HOME/bin/jmod describe $JAVA10_HOME/jmods/java.xml.bind.jmod > java.xml.bind.desc
And here is what I have got: java.xml.bind.desc
Specifically of interest is:
Therefore, dependency is explicit and transitive on Java 10 as well. It seems like it might be added automatically by --add-modules java.xml.bind, otherwise, the modular JVM shouldn't start with missing dependency error, as far as I understand.
Hence, it looks like this task might be a matter of prudence, not a strict requirement.