Re: RFR: JDK-8178037 Move information from jdi-overview.html into jdk.jdi module-info.java

2017-04-19 Thread David Holmes
On 19/04/2017 10:54 PM, Magnus Ihse Bursie wrote: With JDK-8172312, the file src/jdk.jdi/share/classes/jdi-overview.html is no longer included in the generated documentation. The information provided by that file should move to src/jdk.jdi/share/classes/module-info.java instead. Looks good, but

Re: RFR: 8076417: Update test/jdk/asm/AsmSanity.java with modules

2017-04-19 Thread Mandy Chung
> On Apr 19, 2017, at 11:26 AM, Kumar Srinivasan > wrote: > > > Made the change you recommended, and here is the updated webrev > http://cr.openjdk.java.net/~ksrini/8076417/webrev.01/ +1 Mandy

Re: RFR: 8076417: Update test/jdk/asm/AsmSanity.java with modules

2017-04-19 Thread Amy Lu
On 4/20/17 2:26 AM, Kumar Srinivasan wrote: Made the change you recommended, and here is the updated webrev http://cr.openjdk.java.net/~ksrini/8076417/webrev.01/ Thank you Kumar!Looks good. (I'm not official reviewer) Thanks, Amy Thanks Kumar Hi, Kumar As the removed test is the only one

Re: RFR[9]: 8178832: (ref) jdk.lang.ref.disableClearBeforeEnqueue property is ignored

2017-04-19 Thread Kim Barrett
> On Apr 19, 2017, at 2:51 PM, Mandy Chung wrote: > > >> On Apr 19, 2017, at 2:02 AM, Peter Levart wrote: >> >> I wonder if there are (or will be) other places where such silent swallowing >> of run-time exceptions happens or will happen. Wouldn't it be good to "fix" >> Boolean.getBoolean()

Re: RFR[9]: 8178832: (ref) jdk.lang.ref.disableClearBeforeEnqueue property is ignored

2017-04-19 Thread Mandy Chung
> On Apr 19, 2017, at 2:02 AM, Peter Levart wrote: > > I wonder if there are (or will be) other places where such silent swallowing > of run-time exceptions happens or will happen. Wouldn't it be good to "fix" > Boolean.getBoolean() and friends? > > I filed the following bug to track this: >

Re: JDK 9 RFR(s): 8167981: Optional: add notes explaining intended use

2017-04-19 Thread Stuart Marks
Martin wrote: + * The methods {@link #orElse(java.lang.Object) orElse()} and It's sad that in 2017 we still can't write {@link #orElse(T)} ... but ... we can and should write {@link #orElse(Object) orElse(T)} making the source and html more readable (orElse is not nullary) Well we're not going

Re: JDK 9 RFR: 8176168: Performance drop due to SAXParser SymbolTable reset

2017-04-19 Thread huizhe wang
Hi Aleksej, The changes look good. Some changes to the notes in the test may make it a bit clearer on what scenarios are tested: move the current notes for the method testResetEnabled to parseAndCheckReset, and then add scenario description to the three test* methods, for example, testNoFeatur

Re: RFR: 8076417: Update test/jdk/asm/AsmSanity.java with modules

2017-04-19 Thread Kumar Srinivasan
Made the change you recommended, and here is the updated webrev http://cr.openjdk.java.net/~ksrini/8076417/webrev.01/ Thanks Kumar Hi, Kumar As the removed test is the only one test under jdk/asm, it needs to be removed from jdk_other test group: --- a/test/TEST.groups +++ b/test/TEST.grou

Re: RFR: 8076417: Update test/jdk/asm/AsmSanity.java with modules

2017-04-19 Thread Kumar Srinivasan
Ah, yes, good catch. Thanks Amy. Kumar Hi, Kumar As the removed test is the only one test under jdk/asm, it needs to be removed from jdk_other test group: --- a/test/TEST.groups +++ b/test/TEST.groups @@ -269,7 +269,6 @@ javax/transaction \ javax/xml \ -javax/xml/crypto \ -

Re: JDK 9 RFR(s): 8167981: Optional: add notes explaining intended use

2017-04-19 Thread Paul Sandoz
> On 18 Apr 2017, at 20:29, Martin Buchholz wrote: > > + * The methods {@link #orElse(java.lang.Object) orElse()} and > > It's sad that in 2017 we still can't write > {@link #orElse(T)} > ... but ... we can and should write > {@link #orElse(Object) orElse(T)} > making the source and html mo

Re: RFR: JDK-8178037 Move information from jdi-overview.html into jdk.jdi module-info.java

2017-04-19 Thread Mandy Chung
> On Apr 19, 2017, at 5:54 AM, Magnus Ihse Bursie > wrote: > > With JDK-8172312, the file src/jdk.jdi/share/classes/jdi-overview.html is no > longer included in the generated documentation. The information provided by > that file should move to src/jdk.jdi/share/classes/module-info.java inste

Re: "unsafe" instances in sun.nio.fs.WindowsFileSystem

2017-04-19 Thread Brian Burkhalter
[Looping in nio-dev] I can file an issue and look into it. Brian On Apr 18, 2017, at 11:44 PM, Alan Bateman wrote: > On 19/04/2017 05:44, Chan, Sunny wrote: > >> While reading the code for sun.nio.fs.WindowsFileSystemProvider and >> sun.nio.fs.WindowsUserDefinedFileAttributeView, I noticed t

Re: RFR: JDK-8178037 Move information from jdi-overview.html into jdk.jdi module-info.java

2017-04-19 Thread Alan Bateman
On 19/04/2017 13:54, Magnus Ihse Bursie wrote: With JDK-8172312, the file src/jdk.jdi/share/classes/jdi-overview.html is no longer included in the generated documentation. The information provided by that file should move to src/jdk.jdi/share/classes/module-info.java instead. I also took the

Re: RFR: JDK-8178037 Move information from jdi-overview.html into jdk.jdi module-info.java

2017-04-19 Thread Erik Joelsson
Looks good to me. /Erik On 2017-04-19 14:54, Magnus Ihse Bursie wrote: With JDK-8172312, the file src/jdk.jdi/share/classes/jdi-overview.html is no longer included in the generated documentation. The information provided by that file should move to src/jdk.jdi/share/classes/module-info.java

RFR: JDK-8178037 Move information from jdi-overview.html into jdk.jdi module-info.java

2017-04-19 Thread Magnus Ihse Bursie
With JDK-8172312, the file src/jdk.jdi/share/classes/jdi-overview.html is no longer included in the generated documentation. The information provided by that file should move to src/jdk.jdi/share/classes/module-info.java instead. I also took the liberty of removing a bunch of other overview.ht

Re: [9] RFR(S): 8178726: Can't load classes from classpath if it is a UNC share

2017-04-19 Thread Volker Simonis
On Wed, Apr 19, 2017 at 12:22 PM, Alan Bateman wrote: > On 19/04/2017 10:18, Volker Simonis wrote: > >> : >> That's a good suggestion. I've updated the patch with a slightly >> modified comment: >> >> // Use an intermediate File object to construct a URI/URL without >> // authority component as UR

Re: [9] RFR(S): 8178726: Can't load classes from classpath if it is a UNC share

2017-04-19 Thread Alan Bateman
On 19/04/2017 10:18, Volker Simonis wrote: : That's a good suggestion. I've updated the patch with a slightly modified comment: // Use an intermediate File object to construct a URI/URL without // authority component as URLClassPath can't handle URLs with a UNC // server name in the authority c

Re: [9] RFR(S): 8178726: Can't load classes from classpath if it is a UNC share

2017-04-19 Thread Chris Hegarty
> On 19 Apr 2017, at 10:18, Volker Simonis wrote: > >> ... > > That's a good suggestion. I've updated the patch with a slightly > modified comment: > > // Use an intermediate File object to construct a URI/URL without > // authority component as URLClassPath can't handle URLs with a UNC > // s

Re: [9] RFR(S): 8178726: Can't load classes from classpath if it is a UNC share

2017-04-19 Thread Volker Simonis
On Wed, Apr 19, 2017 at 9:03 AM, Alan Bateman wrote: > On 18/04/2017 18:44, Volker Simonis wrote: > > Hi Alan, Chris, > > thanks for your help and feedback. > It seems my fix was indeed "too optimistic". I've only briefly looked into > the errors reported by Chris. The first one is due to a cyclic

Re: RFR[9]: 8178832: (ref) jdk.lang.ref.disableClearBeforeEnqueue property is ignored

2017-04-19 Thread Peter Levart
Hi Mandy, Kim, On 04/17/2017 10:53 PM, Mandy Chung wrote: On Apr 17, 2017, at 1:47 PM, Kim Barrett wrote: Please review this fix for a bug in JDK-8175797: the mechanism provided by that change for reverting to the old behavior of Reference.enqueue (for backward compatibility) does not work. A

Re: [9] RFR(S): 8178726: Can't load classes from classpath if it is a UNC share

2017-04-19 Thread Alan Bateman
On 18/04/2017 18:44, Volker Simonis wrote: Hi Alan, Chris, thanks for your help and feedback. It seems my fix was indeed "too optimistic". I've only briefly looked into the errors reported by Chris. The first one is due to a cyclic dependency between Paths.get() and FileSystems.getDefault().