Gradle 5.0 and Java 11

DJViking · October 30, 2018, 5:32pm

Java enthusiasts will be happy to read that this release supports running Gradle builds with JDK 11

What is this change about actually? I have no problem running Gradle 4.10 with Java 11 to build both modular and non-modular applications.

JavaVersion.VERSION_11 constant along with isJava11() and isJava11Compatible() methods

github.com/gradle/gradle

Java 11 support

opened 04:07PM - 20 Apr 18 UTC

closed 02:51PM - 15 Oct 18 UTC

blindpirate

a:epic

Java 11 would be a LTS (long time support) version. For now, it's still a bit ea…rlier to invest our time into it, since it's still not stable and lack of ecosystem. Some issues I've identified include: - ~ASM throws `IllegalArgumentException` upon Java 11 bytecode.~ - Scala doesn't support it: `object java.lang.Object in compiler mirror not found.` - A bug which is already submitted to Oracle: `File.getAbsolutePath()` isn't affected by ` System.setProperty("user.dir", "")` and daemon needs correct behavior to set environment. ``` System.out.println(new java.io.File("a").getAbsolutePath()); System.setProperty("user.dir", "/User/zhb"); System.out.println(new java.io.File("a").getAbsolutePath()); ``` has different behavior on Java 10 and Java 11. > This is not a bug. The "user.dir" property should never be changed in a running VM. according to JDK team: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8202127 In https://github.com/gradle/gradle/pull/2159 , the environment manipulation was disabled for Java 9+. At that point, JDK team promised to disable reflection access in Java 9 - which didn't happen eventually. On Java 9/10/11, illegal reflection access is actually allowed with an warning. This means that we can use reflection to set environment variable as before - and the warning can be suppressed by putting Gradle jars on `--module-path` then adding `--add-opens java.base/java.util=<GRADLE>`. However, this doesn't mean we should - we shouldn't keep using this dirty hack to set environment since the first day of Gradle. We need another discussion on how to solve this issue.

st_oehme · October 30, 2018, 5:53pm

Not everything worked in 4.10, so we didn’t make an official statement. I’m happy 4.10 works for you already

Topic		Replies	Views
Gradle wants as java version openjdk-11 even if a newer version is installed? . . Help/Discuss	5	1288	March 28, 2023
Current Java 9 status and roadmap Help/Discuss	1	4623	February 5, 2017
Using OpenJDK Early Access builds and Gradle Help/Discuss	4	3343	May 31, 2018
Gradle can't import my Java 8 package because it thinks it's Java 11 Help/Discuss	4	2228	May 3, 2023
Gradle 2.14 deprecating java 6 as runtime Help/Discuss	4	2703	May 11, 2016

Gradle 5.0 and Java 11

Related Topics