finally success again on JDK9

[Jochen Theodorou <bl...@gmx.org>]

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

Re: finally success again on JDK9

[Jochen Theodorou <bl...@gmx.org>]

On 07.04.2017 04:30, Paul King wrote:
> 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.

We will require a JDK9 based build, because we will require JDK9 
specific (but optional) code. So getting the build running under JDK9 
again was the first step for me. Next step is for me fixing the failing 
tests (though I am unsure there is a replacement for the failing grab tests)

bye Jochen

Re: finally success again on JDK9

[Paul King <pa...@asert.com.au>]

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 <bl...@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
>

Re: finally success again on JDK9

[Daniel Sun <re...@hotmail.com>]

Glad to hear the good news ;)

Cheers,
Daniel.Sun



--
View this message in context: http://groovy.329449.n5.nabble.com/finally-success-again-on-JDK9-tp5739646p5739649.html
Sent from the Groovy Dev mailing list archive at Nabble.com.