Hi there, before I throw some time at this, I’d like to check whether anybody knows of an up-to-date reference of what Gradle functionality is supposed to work with the latest build of Java9 (at the time of writing that is
When I run
gradle tasks with it, I immediately get
ExceptionInInitializerError with cause:
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected java.lang.Package java.lang.ClassLoader.getPackages() accessible: module java.base does not "opens java.lang" to unnamed module @7cb502c at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:207) at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:192) at java.base/java.lang.reflect.Method.setAccessible(Method.java:186) at org.gradle.internal.reflect.JavaMethod.<init>(JavaMethod.java:42) at org.gradle.internal.reflect.JavaMethod.<init>(JavaMethod.java:32) at org.gradle.internal.reflect.JavaMethod.<init>(JavaMethod.java:36) at org.gradle.internal.reflect.JavaReflectionUtil.method(JavaReflectionUtil.java:223) at org.gradle.internal.classloader.FilteringClassLoader.<clinit>(FilteringClassLoader.java:49) ... 47 more
What is interesting is that running on TravisCI
9-ea+140 I get a different error (complaining about the Kotlin plugin trying to get
I tried to look at the internet and I saw an announcement that Gradle 3.0 is supposed to work with JDK9, but not with the Jigsaw branch. Now that the Jigsaw branch is merged, does it mean we can not run Gradle on JDK 9 anymore?
Has anybody tried running Gradle on Java8 and cross-compiling to Java9?
Slightly unrelated, the last design document for Java9 support lists a number of features related ot modularization. Are these still current? (as most of them refer to the model/rule based config) The new Java Library plugin separates the API from implementation deps, which is a great first step. Is there a plan to provide DSL for API packages? Any tentative timeline about that?