2018-04-20 22:24 GMT+02:00 André Malo <n...@perlig.de>: > * Luca Toscano wrote: > > > 2018-04-20 7:17 GMT+02:00 Christophe Jaillet > > <christophe.jail...@wanadoo.fr> > > > > >> -Xbootclasspath/p is no longer a supported option. > > >> Error: Could not create the Java Virtual Machine. > > >> Error: A fatal exception has occurred. Program will exit. > > >> > > There was an email thread in dev@ a while ago about it: > > > > https://lists.apache.org/thread.html/e359cacc6b24813af0e2b0cc2ef4ed > 8ac5c5 > >5a05f7c5785221d886e3@%3Cdev.httpd.apache.org%3E > > > > Afaics it ended up nowhere, with the question mark "is Xbootclasspath > > needed or no?" > > I'm positive, that it *was* needed. If it's producing the same output > without that argument these days (i.e. >= java 8), just ditch it. > Otherwise > we might need some version sniffing. Also we should then check if java 9 > produces the same output. > > There have been xalan + xerces issues. They might be even related. I don't > recall if this classpath issue was just some api error or output > formatting > related. However - if it works consistently across installation - it works > (that being the whole point of the java setup). > > Thanks!
Christophe, would you have some time to test Java 9 and see if the build output is good even without Xbootclasspath? I'll try to do the same during the next days.. Luca
