Re: RFR: 8166287: MultiReleaseJarAPI.isMultiReleaseJar(): failure java.nio.file.AccessDeniedException: custom-mr.jar

2016-09-28 Thread Claes Redestad
Michael, Alan, thanks for reviewing. Sure, might as well push to jdk9/dev /Claes On 2016-09-28 14:10, Alan Bateman wrote: On 28/09/2016 11:56, Claes Redestad wrote: Hi, recently added test cases to MultiReleaseJarAPI can cause an AccessDeniedException on some Windows systems, and using a

Re: RFR: 8166287: MultiReleaseJarAPI.isMultiReleaseJar(): failure java.nio.file.AccessDeniedException: custom-mr.jar

2016-09-28 Thread Alan Bateman
On 28/09/2016 11:56, Claes Redestad wrote: Hi, recently added test cases to MultiReleaseJarAPI can cause an AccessDeniedException on some Windows systems, and using a distinct name of the jar generated for each test should avoid this. webrev:

Re: RFR: 8166287: MultiReleaseJarAPI.isMultiReleaseJar(): failure java.nio.file.AccessDeniedException: custom-mr.jar

2016-09-28 Thread Michael Haupt
Hi Claes, thumbs up. Best, Michael > Am 28.09.2016 um 12:56 schrieb Claes Redestad : > > Hi, > > recently added test cases to MultiReleaseJarAPI can cause an > AccessDeniedException on some Windows systems, and using a distinct name of > the jar generated for

RFR: 8166287: MultiReleaseJarAPI.isMultiReleaseJar(): failure java.nio.file.AccessDeniedException: custom-mr.jar

2016-09-28 Thread Claes Redestad
Hi, recently added test cases to MultiReleaseJarAPI can cause an AccessDeniedException on some Windows systems, and using a distinct name of the jar generated for each test should avoid this. webrev: http://cr.openjdk.java.net/~redestad/8166287/webrev.01/ bug: