RFR: 8256299: Implement JEP 396: Strongly Encapsulate JDK Internals by Default [v3]

David Holmes david.holmes at oracle.com
Fri Nov 20 09:29:39 UTC 2020


Hi Alan,

On 20/11/2020 6:04 pm, Alan Bateman wrote:
> On Fri, 20 Nov 2020 07:33:50 GMT, David Holmes <dholmes at openjdk.org> wrote:
> 
>> I'm somewhat surprised by the extent of the other changes given the basic change here is to deprecate the option and change its default. I literally expected to see only 2 simple changes to the functional code: the deprecation warning and the changing of the default value.
> 
> There are interactions with the archiving of the module graph and boot layer. Here's one of the mails from the review of JDK-8244778 that has more context:
> https://mail.openjdk.java.net/pipermail/core-libs-dev/2020-August/068159.html
> The summary is that, as a short term measure until JEP 396 showed up, we agreed to have the maps to support exporting and opening packages for illegal reflective acces archived with the boot layer. Switching the default allows it goes away.

Thanks for the information. I don't understand enough to know why this 
is the case.

Cheers,
David

> -------------
> 
> PR: https://git.openjdk.java.net/jdk/pull/1324
> 


More information about the core-libs-dev mailing list