I am moving a project that uses the JPMS from Oracle JDK10 to OpenJDK11. The app is compiling/running apart from any (un)marshaling operation using JAXB. I am getting the following error: javax.xml.bind.JAXBException: Implementation of J...
In the compile and run tasks, I can effectively override the behavior by add extra command line arguments that definitively set the classpath and module path. In the case of theCreateStartScriptsclass, I can't see a way to override the behavior, since I can't replace the implementation of...
the maven classpath container might add options to any resolved classpath entry When using the mechanism of org.eclipse.jdt.core.IClasspathEntry.getExtraAttributes() with keys from org.eclipse.jdt.core.IClasspathAttribute JDT should immediately respect those for compiling as well as for launching. ...