Better tools for adjusting to strong encapsulation

[Keimpe Bronkhorst]

Thanks, Mark. We're in the middle of collecting necessary --add-opens, 
--add-exports and other options and only making some progress with 
removing the need for them. Warnings in JDK10 seems more appropriate.

Keimpe Bronkhorst
Oracle JDeveloper

On 3/23/2017 2:13 AM, jigsaw-dev-request at openjdk.java.net wrote:
>
> ------------------------------
>
> Message: 4
> Date: Wed, 22 Mar 2017 20:30:00 -0700
> From: mark.reinhold at oracle.com
> To: jigsaw-dev at openjdk.java.net
> Subject: Re: Better tools for adjusting to strong encapsulation
> Message-ID: <20170322203000.424722369 at eggemoggin.niobe.net>
> Content-Type: text/plain
>
> Thanks to everyone for all the feedback on this topic.
>
> It appears that issuing warning messages for illegal-access operations
> enabled by the precise `--add-opens` and `--add-exports` options is a
> bit too aggressive, at least for JDK 9.  Perhaps we can enable that in
> JDK 10 after there's been more time for libraries, frameworks, and even
> the JDK itself to adjust to the realities of strong encapsulation.
>
> For now I suggest that we revert to the previous behavior of these two
> options, so that they do not cause warning messages to be issued.  The
> new `--permit-illegal-access` option will continue to generate warning
> messages, as proposed.  If those messages are a problem in a particular
> scenario then they can be eliminated by switching to an appropriate set
> of `--add-opens` options, which can be constructed from the information
> contained in those messages.
>
> Comments?
>
> - Mark
>