ovy-and-language-level-in-master-tp5739721p5739734.html
Sent from the Groovy Dev mailing list archive at Nabble.com.
On Sat, Apr 8, 2017 at 1:11 AM, Jochen Theodorou wrote:
> Hi all,
>
> so if we want to be serious about JDK9 support and not life with a
> thousands of warnings displayed whenever you try to execute a Groovy
> program or test (44k+ in our build for example)... then we will need JDK9
> specific co
On April 8, 2017 7:35:18 PM GMT+02:00, Jochen Theodorou
wrote:
>On 08.04.2017 16:29, Remi Forax wrote:
>> Jochen,
>> technically, you do not need the jdk 9,
>> you can compile with jdk 8 and have a jar that contains the
>declaration
>> of methods of the jdk 9 you want.
>
>and use -Xbootclasspat
On 08.04.2017 16:29, Remi Forax wrote:
Jochen,
technically, you do not need the jdk 9,
you can compile with jdk 8 and have a jar that contains the declaration
of methods of the jdk 9 you want.
and use -Xbootclasspath/p:path? yes, I guess we can do that. JDK-8177827
will get in the way, but tha
Jochen,
technically, you do not need the jdk 9,
you can compile with jdk 8 and have a jar that contains the declaration of
methods of the jdk 9 you want.
JRuby had worked that way when it was jdk 6 compatible but optionally uses the
java.lang.invoke API.
regards,
Rémi
On April 8, 2017 10:11:51
Hi all,
so if we want to be serious about JDK9 support and not life with a
thousands of warnings displayed whenever you try to execute a Groovy
program or test (44k+ in our build for example)... then we will need
JDK9 specific code.
That means we will have to change our build to support opti
