Looks good to me now.
/Magnus
On 2017-03-09 17:42, Christian Tornqvist wrote:
Updated webrev based on feedback from Magnus Ihse Bursie:
http://cr.openjdk.java.net/~ctornqvi/webrev/8175300/webrev.01/
-Original Message-
From: hotspot-dev [mailto:hotspot-dev-boun...@openjdk.java.net] On
> On Mar 9, 2017, at 2:55 PM, Dan Smith wrote:
>
>
>> On Mar 9, 2017, at 3:48 PM, Mandy Chung wrote:
>>
>> Are you using JDK 9 as the boot JDK or doing bootcycle build?
>
> I think the former, since I don't know what a bootcycle build is?
>
> On Mar 9, 2017, at 3:48 PM, Mandy Chung wrote:
>
> Are you using JDK 9 as the boot JDK or doing bootcycle build?
I think the former, since I don't know what a bootcycle build is?
Steps to reproduce:
$ -> cd ~/Dev/jdk/jdk10
$ -> sh configure
Are you using JDK 9 as the boot JDK or doing bootcycle build?
I file a bug to track this:
https://bugs.openjdk.java.net/browse/JDK-8176469
This warning is emitted when running javac with the patch module path that
overrides jdk.compiler, jdk.rmic and a few other modules but jdk.rmic is not in
On 03/09/2017 11:44 AM, Dan Smith wrote:
During a build, many of these warnings get spit out:
WARNING: Unknown module: jdk.rmic specified in --patch-module
I've been assuming someone would clean this up eventually, but it's been there
for months. Don't see a JBS bug. Is this on someone's
During a build, many of these warnings get spit out:
WARNING: Unknown module: jdk.rmic specified in --patch-module
I've been assuming someone would clean this up eventually, but it's been there
for months. Don't see a JBS bug. Is this on someone's radar?
Or maybe this is somehow a weird quirk
Updated webrev based on feedback from Magnus Ihse Bursie:
http://cr.openjdk.java.net/~ctornqvi/webrev/8175300/webrev.01/
-Original Message-
From: hotspot-dev [mailto:hotspot-dev-boun...@openjdk.java.net] On Behalf Of
Christian Tornqvist
Sent: Tuesday, March 7, 2017 3:03 PM
To: