Gradle not working on Jigsaw
Stephen Felts
stephen.felts at oracle.com
Fri Oct 21 20:37:16 UTC 2016
It's possible to work around the gradle error below by adding
--add-exports-private=java.base/java.io=ALL-UNNAMED to _JAVA_OPTIONS.
It's unfortunate that javac doesn't recognize this option because up until now I had been using one jdk9args file for both java and javac.
The next one that I ran into was a pattern match that needed java.base/java.util.regex.
So the number of these add-exports-private depends on what gradle/groovy code you have in your projects and what underlying java packages they reference.
The list that Kevin sent out in his email yesterday is quite different from what I need.
I'm also running with the daemon so it seems to need java.base/sun.net.www java.base/sun.net.www.protocol.file java.base/java.lang.invoke.
-----Original Message-----
From: Stephen Felts
Sent: Wednesday, October 19, 2016 10:43 PM
To: jigsaw-dev at openjdk.java.net
Subject: Gradle not working on Jigsaw
I have the line
def branch = file('..').name
in build.gradle.
Running 'gradle' on build 140
Jdk-9 - runs fine
JDK-9 Jigsaw gets
* What went wrong:
A problem occurred evaluating root project 'dir'.
> No such property: name for class: java.io.File
To run on Jigsaw, I also need to set _JAVA_OPTIONS to include --add-exports-private=java.base/java.lang=ALL-UNNAMED
--add-exports-private=java.base/java.util=ALL-UNNAMED
More information about the jigsaw-dev
mailing list