JDK9 support

Question

JDK9 support

ben-manes opened this issue 8 years ago · 11 comments

Using 9ea and Gradle 3.0, the plugin has to be disabled due to the error

Caused by: java.lang.NoClassDefFoundError: Could not initialize class net.ltgt.gradle.errorprone.ErrorProneCompiler$SelfFirstClassLoader
        at net.ltgt.gradle.errorprone.ErrorProneCompiler.execute(ErrorProneCompiler.java:51)
        at net.ltgt.gradle.errorprone.ErrorProneCompiler.execute(ErrorProneCompiler.java:25)

Answer 1 · 2016-08-23T10:11:37.000Z

Reproduced.

Looks like the Jvm.current().getToolsJar().… throws an NPE (expected, as there's no tools.jar in JDK 9 any longer), but removing it (using a URLClassLoader with no entries) then fails with an NPE during the compilation, because that System.getProperty("sun.boot.class.path") returns null (see http://openjdk.java.net/jeps/261).

I think Error Prone simply is not compatible with JDK 9 yet.

Answer 2 · 2016-08-23T10:15:44.000Z

See google/error-prone#448 (comment)

We're not yet supporting running on JDK 9.

So, I'll change the plugin to support JDK 9 (i.e. no longer fail when there's no tools.jar), but you'll have to wait for Error Prone to support JDK 9 to be able to actually use it.

Answer 3 · 2016-08-23T10:45:54.000Z

In retrospect, not really knowing how Error Prone will tackle the problem, it's probably safer to wait for them to support JDK 9 and only then update the plugin accordingly. WDYT?

Answer 4 · 2016-08-23T15:51:10.000Z

I'm fine disabling in my build. I think being explicit is reasonable.

Answer 5 · 2017-05-03T10:05:00.000Z

FWIW, 8aa08a8 (shipped in 0.0.9) now handles the case where Jvm.current().getToolsJar() returns null; so with JDK 9 the build should now fail with an explicit error message hinting that the JDK might not be compatible (I can't even make Gradle start with Java 9 though…).

(leaving this issue open as this will need to change anyway once Error Prone supports JDK 9)

Answer 6 · 2017-07-16T23:49:43.000Z

It looks like JDK 9 support is becoming official through the use of the -Xplugin flag: google/error-prone#681

I'd rather wait for the final JDK 9 release before making any change though (if any, having to use the -processorpath could easily conflict with other plugins or JavaCompile tasks' configuration, so maybe this plugin will actually never support JDK 9, by design).

Answer 7 · 2017-09-22T00:54:28.000Z

Finally released so a bunch of tooling is officially busted. ;)

Answer 8 · 2017-10-13T10:11:35.000Z

A PR hits the "no tools.jar" wall junit-team/junit5#961 -- any news on supporting JDK 9?

Answer 9 · 2017-10-13T13:27:07.000Z

Let me have a look at it. It looks like tools.jar is actually not (no longer?) needed with Java 8 (actually, that was probably a requirement of ErrorProne 1.x, remove from 2.x when it started using its own javac; and I recently removed support for Java 7 and ErrorProne 1.x), and ErrorProne would then work in a JDK 9 environment.
Needs more testing…

Answer 10 · 2017-10-13T17:39:25.000Z

I just release v0.0.13 which works with Java 9; but please note that Error Prone does not support JPMS or the --release flag (to guarantee backwards-compatibility with JDK 7 or JDK 8, without the need to use those JDKs when compiling), among other things.

Closing this issue, as things are now on Error Prone's side.

Answer 11 · 2017-10-13T18:08:06.000Z

I just release v0.0.13 which works with Java 9

Thanks Thomas!

please note that Error Prone does not support JPMS or the --release flag (to guarantee backwards-compatibility with JDK 7 or JDK 8, without the need to use those JDKs when compiling), among other things.

Okay for me. :)