New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Take care of jaxb dependencies for Java 9 and newer #162

Open
steffen-wilke opened this Issue Aug 17, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@steffen-wilke
Copy link
Collaborator

steffen-wilke commented Aug 17, 2018

The JAXB APIs are considered to be Java EE APIs, and therefore are no longer contained on the default class path in Java SE 9. In Java 11 they are completely removed from the JDK.

I think we need to reference the maven libraries to properly solve this in a future prove manner.

https://stackoverflow.com/questions/43574426/how-to-resolve-java-lang-noclassdeffounderror-javax-xml-bind-jaxbexception-in-j

@TheRamenChef

This comment has been minimized.

Copy link
Collaborator

TheRamenChef commented Oct 16, 2018

Considering that LITIEngine is built with Gradle, this answer could be useful.

@KennFatt

This comment has been minimized.

Copy link
Contributor

KennFatt commented Nov 7, 2018

Any workaround with this issue? I'm using JDK 10 and can't run utiLITI.

These is all my modules:

java.activation@10
java.base@10
java.compiler@10
java.corba@10
java.datatransfer@10
java.desktop@10
java.instrument@10
java.jnlp@10
java.logging@10
java.management@10
java.management.rmi@10
java.naming@10
java.prefs@10
java.rmi@10
java.scripting@10
java.se@10
java.se.ee@10
java.security.jgss@10
java.security.sasl@10
java.smartcardio@10
java.sql@10
java.sql.rowset@10
java.transaction@10

java.xml@10

java.xml.bind@10

java.xml.crypto@10
java.xml.ws@10
java.xml.ws.annotation@10

javafx.base@10
javafx.controls@10
javafx.deploy@10
javafx.fxml@10
javafx.graphics@10
javafx.media@10
javafx.swing@10
javafx.web@10
jdk.accessibility@10
jdk.aot@10
jdk.attach@10
jdk.charsets@10
jdk.compiler@10
jdk.crypto.cryptoki@10
jdk.crypto.ec@10
jdk.crypto.mscapi@10
jdk.deploy@10
jdk.deploy.controlpanel@10
jdk.dynalink@10
jdk.editpad@10
jdk.hotspot.agent@10
jdk.httpserver@10
jdk.incubator.httpclient@10
jdk.internal.ed@10
jdk.internal.jvmstat@10
jdk.internal.le@10
jdk.internal.opt@10
jdk.internal.vm.ci@10
jdk.internal.vm.compiler@10
jdk.internal.vm.compiler.management@10
jdk.jartool@10
jdk.javadoc@10
jdk.javaws@10
jdk.jcmd@10
jdk.jconsole@10
jdk.jdeps@10
jdk.jdi@10
jdk.jdwp.agent@10
jdk.jfr@10
jdk.jlink@10
jdk.jshell@10
jdk.jsobject@10
jdk.jstatd@10
jdk.localedata@10
jdk.management@10
jdk.management.agent@10
jdk.management.cmm@10
jdk.management.jfr@10
jdk.management.resource@10
jdk.naming.dns@10
jdk.naming.rmi@10
jdk.net@10
jdk.pack@10
jdk.packager@10
jdk.packager.services@10
jdk.plugin@10
jdk.plugin.server@10
jdk.rmic@10
jdk.scripting.nashorn@10
jdk.scripting.nashorn.shell@10
jdk.sctp@10
jdk.security.auth@10
jdk.security.jgss@10
jdk.snmp@10
jdk.unsupported@10
jdk.xml.bind@10
jdk.xml.dom@10
jdk.xml.ws@10
jdk.zipfs@10
oracle.desktop@10
oracle.net@10

Where the java.xml.bind is included there

@TheRamenChef

This comment has been minimized.

Copy link
Collaborator

TheRamenChef commented Jan 4, 2019

It's still not working for me.

@TheRamenChef TheRamenChef reopened this Jan 4, 2019

@steffen-wilke

This comment has been minimized.

Copy link
Collaborator

steffen-wilke commented Jan 13, 2019

It's still not working for me.

Which Java Version are you using?
Which LITIengine version are you using?
What exactly is not working?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment