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.
