Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

On 28 Jun 2017, at 17:31, Alan Bateman wrote: > > On 28/06/2017 14:46, Robert Gibson wrote: >> Sure. >> (It actually doesn't make any difference how the app is started, browser or >> javaws, results are the same in either case.) >> >> > Can you confirm that this is

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

On 28/06/2017 14:46, Robert Gibson wrote: Sure. (It actually doesn't make any difference how the app is started, browser or javaws, results are the same in either case.) Can you confirm that this is Windows only? Andy tells me that javaws.exe is the equivalent of javaw.exe rather than

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

> On 28 Jun 2017, at 10:57, Alan Bateman wrote: > If the illegal access is succeeding then it means Java Web Start has picked > up the option that you added via Control Panel. I can't tell if you are > opened the JNLP in the browser or using the `javaws` CLI but I

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

On 28/06/2017 08:54, Robert Gibson wrote: : Thanks for the follow-up: the debug option doesn't seem to work, bug report filed as 9049772 - hope it doesn't get targeted to 10 ;) If the illegal access is succeeding then it means Java Web Start has picked up the option that you added via Control

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

> On 27 Jun 2017, at 10:18, Alan Bateman wrote: > > > >> On 27/06/2017 08:46, Robert Gibson wrote: >> : >> Hi Alan, >> Thanks for your quick response. No debug option? >> > Not in the JNLP but you should be able to use the Java Control Panel to add >

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

On 27/06/2017 08:46, Robert Gibson wrote: : Hi Alan, Thanks for your quick response. No debug option? Not in the JNLP but you should be able to use the Java Control Panel to add `--illegal-access=debug`. -Alan.

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

On 27 Jun 2017, at 09:34, Alan Bateman wrote: > >> On 27/06/2017 08:24, Robert Gibson wrote: >> Hi Mark, >> What is the intended interaction between this proposal and Java Web Start? >> I'm testing with JDK EA build 175 and it looks like a VM launched through >> Web

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

On 27/06/2017 08:24, Robert Gibson wrote: Hi Mark, What is the intended interaction between this proposal and Java Web Start? I'm testing with JDK EA build 175 and it looks like a VM launched through Web Start is running with --illegal-access=deny, with no possibility of changing it - is this

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

Hi Mark, What is the intended interaction between this proposal and Java Web Start? I'm testing with JDK EA build 175 and it looks like a VM launched through Web Start is running with --illegal-access=deny, with no possibility of changing it - is this by design? (I have filed a few bugs in this

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

Hi, I think the fine-tuning is right to the point now. Allows most of what was allowed in JDK8, but no more than that. Regards, Peter On 06/05/2017 08:45 PM, mark.reinh...@oracle.com wrote: (Thanks for all the feedback on the initial proposal [1]. Here's a revised version, which

RE: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

The new format is missing information that was useful in the earlier -Dsun.reflect.debugModuleAccessChecks=true. It printed something like 'java.base does not "opens java.text" to unnamed module ...' so it was really obvious what option was needed. -Original Message- From: jigsaw-dev

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

Hi, I'm a new poster to this list. I'm actively working on getting Gradle to work on JDK 9, and I also think this proposal strikes a very good balance between pragmatism (don't just break people today) and getting developers motivated to clean up their code for the future. Thank you, Pepper

Re: Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

I think this is the most pragmatic and reasoned middle ground one could possibly imagine. I agree with the finely-tuned choices, specifically: - Not going completely silent. Some asked for the ability to completely shut off the warnings. This goes a little too far to one extreme. There

Proposal (revised): Allow illegal access to internal APIs by default in JDK 9

(Thanks for all the feedback on the initial proposal [1]. Here's a revised version, which incorporates some of the suggestions received and includes a bit more advice. An implementation is already available for testing in the Jigsaw EA builds [2]. Further comments welcome!) Over time, as