groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul King <pa...@asert.com.au>
Subject Re: finally success again on JDK9
Date Fri, 07 Apr 2017 02:30:41 GMT
Good news Jochen!

>From what I understand, the --permit-illegal-access option will be gone for
JDK10+, so we need to keep looking at further restructuring/rework at some
point down the track. Is that also your understanding? It definitely buys
us more time though.

Cheers, Paul.

On Fri, Apr 7, 2017 at 8:58 AM, Jochen Theodorou <blackdrag@gmx.org> wrote:

> Hi all,
>
> So today I finally found out how to run our build on a recent JDK9:
> https://scans.gradle.com/s/bawrmwhk5f33m
>
> The part I could really kick myself... and a lot of gradle people for is
> the usage of _JAVA_OPTIONS. This is can be used to set JVM arguments to
> daemons and the initial forked JVM used by gradle. So I am using
>
> export _JAVA_OPTIONS='-XX:+IgnoreUnrecognizedVMOptions
> --permit-illegal-access'
>
> and org.gradle.jvmargs unset in gradle.properties
>
> The option --permit-illegal-access is new in jigsaw 163 and prevents us
> from having to use add-opens for each an every module.  But at the prize of
> having a ton of messages like this one:
>
> WARNING: Illegal access by org.codehaus.groovy.reflection.CachedConstructor$1
> (file:/home/blackdrag/coding/groovy/commit/target/classes/main/) to
> constructor java.util.LinkedHashMap$LinkedKeySet(java.util.LinkedHashMap)
> (permitted by --permit-illegal-access)
>
> bye Jochen
>

Mime
View raw message