On 06/10/2016 17:28, Phil Race wrote:
OK .. so long as there's no --add-modules needed for that.
Seems to work. Updated webrev :-
http://cr.openjdk.java.net/~prr/8167126.1/
No --add-modules. The updated webrev looks okay to me.
-Alan
OK .. so long as there's no --add-modules needed for that.
Seems to work. Updated webrev :- http://cr.openjdk.java.net/~prr/8167126.1/
-phil.
On 10/06/2016 09:04 AM, Alan Bateman wrote:
On 06/10/2016 16:58, Phil Race wrote:
Similar modules were on the BOOT list.
Can you explain what each of
On 06/10/2016 16:58, Phil Race wrote:
Similar modules were on the BOOT list.
Can you explain what each of these lists are and the implications
of being (and not being) listed on each of them ?
-phil.
The BOOT_MODULES list is the list of modules defined to the boot loader,
the PLATFORM_MODULES
Similar modules were on the BOOT list.
Can you explain what each of these lists are and the implications
of being (and not being) listed on each of them ?
-phil.
On 10/06/2016 12:24 AM, Alan Bateman wrote:
On 05/10/2016 23:01, Phil Race wrote:
Webrev :
On 05/10/2016 23:01, Phil Race wrote:
Webrev : http://cr.openjdk.java.net/~prr/8167126/
The upcoming jigsaw changes to limit use of setAccessible [1] mean
that some work-arounds for non-SE API users will be broken.
To provide for continued access to the capability (albeit via a
different
Webrev : http://cr.openjdk.java.net/~prr/8167126/
The upcoming jigsaw changes to limit use of setAccessible [1] mean
that some work-arounds for non-SE API users will be broken.
To provide for continued access to the capability (albeit via a
different package+class name) this fix adds a
