Yes, Gradle, Groovy and other third party libraries Gradle uses are broken
since the changes to enforce strong encapsulation at runtime (preventing
calls to setAccessible). I already raised the concern here, saying we have
no clear idea of the impact of such a change at a larger scale, but it
totally broke our efforts, and that's kind of depressing. We'll figure it
out, I hope, but unfortunately we have no bandwidth to do it now. We're
gladly accepting pull requests, though :)
2016-10-20 8:57 GMT+02:00 Alan Bateman <alan.bate...@oracle.com>:
> On 20/10/2016 03:42, Stephen Felts wrote:
>
> 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
>>
> I can't tell if this is Groovy or Gradle but if you run with
> -Dsun.reflect.debugModuleAccessChecks=true then it might reveal a stack
> trace where the exception (IllegalAccessException or
> InaccessibleObjectException) is caught and lost. There are folks from these
> products on this list and I'm sure they can direct us to the right place to
> submit an issue. There is already GRADLE-3565 [1].
>
> -Alan
>
> [1] https://issues.gradle.org/browse/GRADLE-3565
>
