groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Uwe Schindler <uschind...@apache.org>
Subject Re: About the tests failed on JDK16
Date Sun, 13 Jun 2021 12:37:57 GMT
Hi,

In JDK 17 the illegal-access flag is ignored and you can't open the internals anymore. So
you need a long term solution.

Uww

Am June 13, 2021 9:22:17 AM UTC schrieb Daniel Sun <sunlan@apache.org>:
>FYI. "the default value of the launcher option --illegal-access is now
>deny rather than permit"
>
>See also
>https://www.oracle.com/java/technologies/javase/16-all-relnotes.html
>
>➜ JEP 396: Strongly Encapsulate JDK Internals by Default
>Strongly encapsulate all internal elements of the JDK by default,
>except for critical internal APIs such as sun.misc.Unsafe. Allow end
>users to choose the relaxed strong encapsulation that has been the
>default since JDK 9.
>
>With this change, the default value of the launcher option
>--illegal-access is now deny rather than permit. As a consequence,
>existing code that uses most internal classes, methods, or fields of
>the JDK will fail to run. Such code can be made to run on JDK 16 by
>specifying --illegal-access=permit. That option will, however, be
>removed in a future release.
>
>On 2021/06/13 09:07:01, Daniel Sun <sunlan@apache.org> wrote: 
>> Hi all,
>> 
>>    I created a branch[1] to try running tests with JDK16, and I found
>39 tests failed[2]. If somebody have some spare time, let's look into
>the issues and try to fix them together.
>> 
>> [1] https://github.com/apache/groovy/tree/danielsun/tweak-build
>> [2] https://travis-ci.com/github/apache/groovy/jobs/513334181
>> 
>> Cheers,
>> Daniel Sun
>> 

Mime
View raw message