Bug#873249: FTBFS with Java 9: javadoc classpath with maven?
On Sat, Aug 26, 2017 at 12:25:16PM +0200, Emmanuel Bourg wrote: > With Java 8 a warning was displayed, but with Java 9 it's now > an error. The only workaround I've found besides fixing the classpath is > > Do you know how many packages are affected by this issue? I'd guess ~4 of the ~50 I looked at, so maybe 30 packages total? I can't grep up a better answer as many packages fail their build before getting to the javadoc generation. This one specifically is weird as it's maven, and maven is probably supposed to be using the same classpath for the build as for the javadoc generation. And the main build has succeeded, or we wouldn't be here.
Bug#873249: FTBFS with Java 9: javadoc classpath with maven?
Hi Chris, Le 25/08/2017 à 21:41, Chris West a écrit : > A number of packages seem to be failing to find classes during their > javadoc build, but they are mostly ant based and I was hoping it was > just bugs in the build file, not a scary change in the way the javadoc > tool works. I have no idea what's going on here. Thanks a lot for the Java 9 FTBFS analysis! I got a quick look at this javadoc issue, javadoc became more strict wrt to missing class on the classpath. With Java 8 a warning was displayed, but with Java 9 it's now an error. The only workaround I've found besides fixing the classpath is to add the new -Xold javadoc option to revert to the Java 8 behavior. Do you know how many packages are affected by this issue? Emmanuel Bourg
Bug#873249: FTBFS with Java 9: javadoc classpath with maven?
Source: uimaj Version: 2.10.0 Severity: normal User: debian-j...@lists.debian.org Usertags: default-java9 This package fails to build with default-jdk pointing to openjdk-9-jdk. The wiki has some common problems and their solutions: https://wiki.debian.org/Java/Java9Pitfalls A number of packages seem to be failing to find classes during their javadoc build, but they are mostly ant based and I was hoping it was just bugs in the build file, not a scary change in the way the javadoc tool works. I have no idea what's going on here. If you work it out, please update the wiki! Build log: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:aggregate (default-cli) on project uimaj: An error has occurred in JavaDocs report generation: [ERROR] Exit code: 1 - /build/uimaj-2.10.0/uimaj-examples/src/main/java/org/apache/uima/examples/xmi/XmiEcoreCasConsumer.java:44: error: package org.eclipse.emf.common.util does not exist [ERROR] import org.eclipse.emf.common.util.URI; ... Example from an ant build (velocity-tools): [javadoc] Constructing Javadoc information... [javadoc] /build/velocity-tools-2.0/src/main/java/org/apache/velocity/tools/ClassUtils.java:39: error: package org.apache.velocity.util does not exist Cheers, Chris.
