JDK 11 Early Access build 15 is available for download.

2018-05-29 Thread Rory O'Donnell 

Hi Benedikt,

**JDK 11 EA build 15 , *under both the GPL and Oracle EA licenses, 
is now available at **http://jdk.java.net/11**. **

*

 * Newly approved Schedule, status & features
 o http://openjdk.java.net/projects/jdk/11/
 * Release Notes:
 o http://jdk.java.net/11/release-notes
 * Summary of changes
 o http://jdk.java.net/11/changes

*Notable changes in JDK 11 EA builds since last email:*

 * b15 - JDK-8201627 
   - Kerberos sequence number issues
 * b13 - JDK-8200146 
   - Removal of appletviewer launcher
 o deprecated in JDK 9 and has been removed in this release
 * b13 - JDK-8201793 
   - java.lang.ref.Reference does not support cloning

**

**

JEPs proposed to target JDK 11 (review ends 2018/05/31 23:00 UTC)

   330: Launch Single-File Source-Code Programs
   

   JEPs targeted to JDK 11, so far

   309: Dynamic Class-File Constants 
   318: Epsilon: A No-Op Garbage Collector
   
   320: Remove the Java EE and CORBA Modules
   
   321: HTTP Client (Standard) 
   323: Local-Variable Syntax for Lambda Parameters
   
   324: Key Agreement with Curve25519 and Curve448
   
   327: Unicode 10 
   328: Flight Recorder 
   329: ChaCha20 and Poly1305 Cryptographic Algorithms
   

Finally, Initial TLSv1.3 implementation Released to the Open Sandbox. 
Please note well: this branch is under
very active development and is not final by any means. Also note: by 
releasing this code, we are not committing
a specific release or timeframe. We will continue development and fixing 
bugs until the code is ready for inclusion

in the JDK. We welcome your feedback, more info [1]


Regards,
Rory

[1] 
http://mail.openjdk.java.net/pipermail/security-dev/2018-May/017139.html


--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland

Re: [release-plugin] Unit test failures

2018-05-29 Thread sebb 
On 29 May 2018 at 02:58, Rob Tompkins  wrote:
> It looks like this has to do with java setting up symbolic links on a windows 
> machine. Clearly this is something that we’ll want to overcome, but I’m not 
> certain how to accommodate this. It seems that:
>
> Files.createSymbolicLink
>
> may not work on Windows. It looks like Apache Storm may have seen this before 
> with https://issues.apache.org/jira/browse/STORM-1193.
>
> Curious if anyone else on the list might have any suggestions here? Also, 
> I’ll try to dig around in the maven codebases to see if they use it anywhere.

Why should the Commons code set up links at all?

> -Rob
>
>> On May 28, 2018, at 1:07 PM, Gary Gregory  wrote:
>>
>> I pulled the latest and I get:
>>
>> [INFO] Preparing to stage distributions
>> [INFO] Checking out dist from: scm:svn:
>> https://dist.apache.org/repos/dist/dev/commons/release-plugin
>> Executing: cmd.exe /X /C "svn --non-interactive checkout
>> https://dist.apache.org/repos/dist/dev/commons/release-plugin
>> C:\vcs\git\apache\commons\commons-release-plugin\target\testing-commons-release-plugin\scm"
>> Working directory:
>> C:\vcs\git\apache\commons\commons-release-plugin\target\testing-commons-release-plugin
>> [INFO] Copying RELEASE-NOTES.txt to working directory.
>> [ERROR] Could not build HEADER and README html files
>> java.nio.file.FileSystemException:
>> C:\vcs\git\apache\commons\commons-release-plugin\target\testing-commons-release-plugin\scm\source\HEADER.html:
>> A required privilege is not held by the client.
>>
>>at
>> sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
>>at
>> sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
>>at
>> sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
>>at
>> sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(WindowsFileSystemProvider.java:585)
>>at java.nio.file.Files.createSymbolicLink(Files.java:1043)
>>at
>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.buildSymbolicLinks(CommonsDistributionStagingMojo.java:342)
>>at
>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.buildReadmeAndHeaderHtmlFiles(CommonsDistributionStagingMojo.java:319)
>>at
>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.copyDistributionsIntoScmDirectoryStructure(CommonsDistributionStagingMojo.java:274)
>>at
>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.execute(CommonsDistributionStagingMojo.java:164)
>>at
>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojoTest.testSuccess(CommonsDistributionStagingMojoTest.java:77)
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>at java.lang.reflect.Method.invoke(Method.java:498)
>>at
>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>>at
>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>>at
>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>>at
>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>>at
>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>>at
>> org.apache.maven.plugin.testing.MojoRule$2.evaluate(MojoRule.java:308)
>>at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>>at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>>at
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>>at
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>>at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>>at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>>at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>>at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>>at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>>at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>>at
>> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
>>at
>> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
>>at
>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
>>at
>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
>>at
>> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379)
>>at
>> org.apache

Re: [release-plugin] Unit test failures

2018-05-29 Thread Rob Tompkins 



> On May 29, 2018, at 6:01 AM, sebb  wrote:
> 
>> On 29 May 2018 at 02:58, Rob Tompkins  wrote:
>> It looks like this has to do with java setting up symbolic links on a 
>> windows machine. Clearly this is something that we’ll want to overcome, but 
>> I’m not certain how to accommodate this. It seems that:
>> 
>> Files.createSymbolicLink
>> 
>> may not work on Windows. It looks like Apache Storm may have seen this 
>> before with https://issues.apache.org/jira/browse/STORM-1193.
>> 
>> Curious if anyone else on the list might have any suggestions here? Also, 
>> I’ll try to dig around in the maven codebases to see if they use it anywhere.
> 
> Why should the Commons code set up links at all?

I’m ok with copying the readme.html and header.html in the dist locations to 
all three directories root, binaries, and source. I was merely trying to keep 
things looking as they are today. 

-Rob

> 
>> -Rob
>> 
>>> On May 28, 2018, at 1:07 PM, Gary Gregory  wrote:
>>> 
>>> I pulled the latest and I get:
>>> 
>>> [INFO] Preparing to stage distributions
>>> [INFO] Checking out dist from: scm:svn:
>>> https://dist.apache.org/repos/dist/dev/commons/release-plugin
>>> Executing: cmd.exe /X /C "svn --non-interactive checkout
>>> https://dist.apache.org/repos/dist/dev/commons/release-plugin
>>> C:\vcs\git\apache\commons\commons-release-plugin\target\testing-commons-release-plugin\scm"
>>> Working directory:
>>> C:\vcs\git\apache\commons\commons-release-plugin\target\testing-commons-release-plugin
>>> [INFO] Copying RELEASE-NOTES.txt to working directory.
>>> [ERROR] Could not build HEADER and README html files
>>> java.nio.file.FileSystemException:
>>> C:\vcs\git\apache\commons\commons-release-plugin\target\testing-commons-release-plugin\scm\source\HEADER.html:
>>> A required privilege is not held by the client.
>>> 
>>>   at
>>> sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
>>>   at
>>> sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
>>>   at
>>> sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
>>>   at
>>> sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(WindowsFileSystemProvider.java:585)
>>>   at java.nio.file.Files.createSymbolicLink(Files.java:1043)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.buildSymbolicLinks(CommonsDistributionStagingMojo.java:342)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.buildReadmeAndHeaderHtmlFiles(CommonsDistributionStagingMojo.java:319)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.copyDistributionsIntoScmDirectoryStructure(CommonsDistributionStagingMojo.java:274)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.execute(CommonsDistributionStagingMojo.java:164)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojoTest.testSuccess(CommonsDistributionStagingMojoTest.java:77)
>>>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>   at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>   at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>   at java.lang.reflect.Method.invoke(Method.java:498)
>>>   at
>>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>>>   at
>>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>>>   at
>>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>>>   at
>>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>>>   at
>>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>>>   at
>>> org.apache.maven.plugin.testing.MojoRule$2.evaluate(MojoRule.java:308)
>>>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>>>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>>>   at
>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>>>   at
>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>>>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>>>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>>>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>>>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>>>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>>>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>>>   at
>>> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
>>>   at
>>> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
>>>   at
>>> org.apac

Re: [release-plugin] Unit test failures

2018-05-29 Thread Rob Tompkins 
@Gary - let me know how things run now. 

> On May 29, 2018, at 6:01 AM, sebb  wrote:
> 
>> On 29 May 2018 at 02:58, Rob Tompkins  wrote:
>> It looks like this has to do with java setting up symbolic links on a 
>> windows machine. Clearly this is something that we’ll want to overcome, but 
>> I’m not certain how to accommodate this. It seems that:
>> 
>> Files.createSymbolicLink
>> 
>> may not work on Windows. It looks like Apache Storm may have seen this 
>> before with https://issues.apache.org/jira/browse/STORM-1193.
>> 
>> Curious if anyone else on the list might have any suggestions here? Also, 
>> I’ll try to dig around in the maven codebases to see if they use it anywhere.
> 
> Why should the Commons code set up links at all?
> 
>> -Rob
>> 
>>> On May 28, 2018, at 1:07 PM, Gary Gregory  wrote:
>>> 
>>> I pulled the latest and I get:
>>> 
>>> [INFO] Preparing to stage distributions
>>> [INFO] Checking out dist from: scm:svn:
>>> https://dist.apache.org/repos/dist/dev/commons/release-plugin
>>> Executing: cmd.exe /X /C "svn --non-interactive checkout
>>> https://dist.apache.org/repos/dist/dev/commons/release-plugin
>>> C:\vcs\git\apache\commons\commons-release-plugin\target\testing-commons-release-plugin\scm"
>>> Working directory:
>>> C:\vcs\git\apache\commons\commons-release-plugin\target\testing-commons-release-plugin
>>> [INFO] Copying RELEASE-NOTES.txt to working directory.
>>> [ERROR] Could not build HEADER and README html files
>>> java.nio.file.FileSystemException:
>>> C:\vcs\git\apache\commons\commons-release-plugin\target\testing-commons-release-plugin\scm\source\HEADER.html:
>>> A required privilege is not held by the client.
>>> 
>>>   at
>>> sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
>>>   at
>>> sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
>>>   at
>>> sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
>>>   at
>>> sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(WindowsFileSystemProvider.java:585)
>>>   at java.nio.file.Files.createSymbolicLink(Files.java:1043)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.buildSymbolicLinks(CommonsDistributionStagingMojo.java:342)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.buildReadmeAndHeaderHtmlFiles(CommonsDistributionStagingMojo.java:319)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.copyDistributionsIntoScmDirectoryStructure(CommonsDistributionStagingMojo.java:274)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo.execute(CommonsDistributionStagingMojo.java:164)
>>>   at
>>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojoTest.testSuccess(CommonsDistributionStagingMojoTest.java:77)
>>>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>   at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>   at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>   at java.lang.reflect.Method.invoke(Method.java:498)
>>>   at
>>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>>>   at
>>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>>>   at
>>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>>>   at
>>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>>>   at
>>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>>>   at
>>> org.apache.maven.plugin.testing.MojoRule$2.evaluate(MojoRule.java:308)
>>>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>>>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>>>   at
>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>>>   at
>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>>>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>>>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>>>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>>>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>>>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>>>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>>>   at
>>> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
>>>   at
>>> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
>>>   at
>>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
>>>   at
>>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Pro

Re: [release-plugin] Unit test failures

2018-05-29 Thread Gary Gregory 
On Tue, May 29, 2018 at 7:01 AM, Rob Tompkins  wrote:

> @Gary - let me know how things run now.
>

The build passes now with 'mvn clean install site -Danimal.sniffer.skip'

Thank you,
Gary


>
> > On May 29, 2018, at 6:01 AM, sebb  wrote:
> >
> >> On 29 May 2018 at 02:58, Rob Tompkins  wrote:
> >> It looks like this has to do with java setting up symbolic links on a
> windows machine. Clearly this is something that we’ll want to overcome, but
> I’m not certain how to accommodate this. It seems that:
> >>
> >> Files.createSymbolicLink
> >>
> >> may not work on Windows. It looks like Apache Storm may have seen this
> before with https://issues.apache.org/jira/browse/STORM-1193.
> >>
> >> Curious if anyone else on the list might have any suggestions here?
> Also, I’ll try to dig around in the maven codebases to see if they use it
> anywhere.
> >
> > Why should the Commons code set up links at all?
> >
> >> -Rob
> >>
> >>> On May 28, 2018, at 1:07 PM, Gary Gregory 
> wrote:
> >>>
> >>> I pulled the latest and I get:
> >>>
> >>> [INFO] Preparing to stage distributions
> >>> [INFO] Checking out dist from: scm:svn:
> >>> https://dist.apache.org/repos/dist/dev/commons/release-plugin
> >>> Executing: cmd.exe /X /C "svn --non-interactive checkout
> >>> https://dist.apache.org/repos/dist/dev/commons/release-plugin
> >>> C:\vcs\git\apache\commons\commons-release-plugin\target\
> testing-commons-release-plugin\scm"
> >>> Working directory:
> >>> C:\vcs\git\apache\commons\commons-release-plugin\target\
> testing-commons-release-plugin
> >>> [INFO] Copying RELEASE-NOTES.txt to working directory.
> >>> [ERROR] Could not build HEADER and README html files
> >>> java.nio.file.FileSystemException:
> >>> C:\vcs\git\apache\commons\commons-release-plugin\target\
> testing-commons-release-plugin\scm\source\HEADER.html:
> >>> A required privilege is not held by the client.
> >>>
> >>>   at
> >>> sun.nio.fs.WindowsException.translateToIOException(
> WindowsException.java:86)
> >>>   at
> >>> sun.nio.fs.WindowsException.rethrowAsIOException(
> WindowsException.java:97)
> >>>   at
> >>> sun.nio.fs.WindowsException.rethrowAsIOException(
> WindowsException.java:102)
> >>>   at
> >>> sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(
> WindowsFileSystemProvider.java:585)
> >>>   at java.nio.file.Files.createSymbolicLink(Files.java:1043)
> >>>   at
> >>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
> .buildSymbolicLinks(CommonsDistributionStagingMojo.java:342)
> >>>   at
> >>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
> .buildReadmeAndHeaderHtmlFiles(CommonsDistributionStagingMojo.java:319)
> >>>   at
> >>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
> .copyDistributionsIntoScmDirectoryStructure(CommonsDistributionStagingMojo
> .java:274)
> >>>   at
> >>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
> .execute(CommonsDistributionStagingMojo.java:164)
> >>>   at
> >>> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
> Test.testSuccess(CommonsDistributionStagingMojoTest.java:77)
> >>>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>   at
> >>> sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> >>>   at
> >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> >>>   at java.lang.reflect.Method.invoke(Method.java:498)
> >>>   at
> >>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
> FrameworkMethod.java:50)
> >>>   at
> >>> org.junit.internal.runners.model.ReflectiveCallable.run(
> ReflectiveCallable.java:12)
> >>>   at
> >>> org.junit.runners.model.FrameworkMethod.invokeExplosively(
> FrameworkMethod.java:47)
> >>>   at
> >>> org.junit.internal.runners.statements.InvokeMethod.
> evaluate(InvokeMethod.java:17)
> >>>   at
> >>> org.junit.internal.runners.statements.RunBefores.
> evaluate(RunBefores.java:26)
> >>>   at
> >>> org.apache.maven.plugin.testing.MojoRule$2.evaluate(MojoRule.java:308)
> >>>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> >>>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> >>>   at
> >>> org.junit.runners.BlockJUnit4ClassRunner.runChild(
> BlockJUnit4ClassRunner.java:78)
> >>>   at
> >>> org.junit.runners.BlockJUnit4ClassRunner.runChild(
> BlockJUnit4ClassRunner.java:57)
> >>>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> >>>   at org.junit.runners.ParentRunner$1.schedule(
> ParentRunner.java:71)
> >>>   at org.junit.runners.ParentRunner.runChildren(
> ParentRunner.java:288)
> >>>   at org.junit.runners.ParentRunner.access$000(
> ParentRunner.java:58)
> >>>   at org.junit.runners.ParentRunner$2.evaluate(
> ParentRunner.java:268)
> >>>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> >>>

Re: [release-plugin] Unit test failures

2018-05-29 Thread Rob Tompkins 



> On May 29, 2018, at 10:16 AM, Gary Gregory  wrote:
> 
>> On Tue, May 29, 2018 at 7:01 AM, Rob Tompkins  wrote:
>> 
>> @Gary - let me know how things run now.
>> 
> 
> The build passes now with 'mvn clean install site -Danimal.sniffer.skip'
> 

Do you have an opinion on the symbolic links in the distributions svn repos?

-Rob

> Thank you,
> Gary
> 
> 
>> 
 On May 29, 2018, at 6:01 AM, sebb  wrote:
 
 On 29 May 2018 at 02:58, Rob Tompkins  wrote:
 It looks like this has to do with java setting up symbolic links on a
>> windows machine. Clearly this is something that we’ll want to overcome, but
>> I’m not certain how to accommodate this. It seems that:
 
 Files.createSymbolicLink
 
 may not work on Windows. It looks like Apache Storm may have seen this
>> before with https://issues.apache.org/jira/browse/STORM-1193.
 
 Curious if anyone else on the list might have any suggestions here?
>> Also, I’ll try to dig around in the maven codebases to see if they use it
>> anywhere.
>>> 
>>> Why should the Commons code set up links at all?
>>> 
 -Rob
 
> On May 28, 2018, at 1:07 PM, Gary Gregory 
>> wrote:
> 
> I pulled the latest and I get:
> 
> [INFO] Preparing to stage distributions
> [INFO] Checking out dist from: scm:svn:
> https://dist.apache.org/repos/dist/dev/commons/release-plugin
> Executing: cmd.exe /X /C "svn --non-interactive checkout
> https://dist.apache.org/repos/dist/dev/commons/release-plugin
> C:\vcs\git\apache\commons\commons-release-plugin\target\
>> testing-commons-release-plugin\scm"
> Working directory:
> C:\vcs\git\apache\commons\commons-release-plugin\target\
>> testing-commons-release-plugin
> [INFO] Copying RELEASE-NOTES.txt to working directory.
> [ERROR] Could not build HEADER and README html files
> java.nio.file.FileSystemException:
> C:\vcs\git\apache\commons\commons-release-plugin\target\
>> testing-commons-release-plugin\scm\source\HEADER.html:
> A required privilege is not held by the client.
> 
>  at
> sun.nio.fs.WindowsException.translateToIOException(
>> WindowsException.java:86)
>  at
> sun.nio.fs.WindowsException.rethrowAsIOException(
>> WindowsException.java:97)
>  at
> sun.nio.fs.WindowsException.rethrowAsIOException(
>> WindowsException.java:102)
>  at
> sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(
>> WindowsFileSystemProvider.java:585)
>  at java.nio.file.Files.createSymbolicLink(Files.java:1043)
>  at
> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
>> .buildSymbolicLinks(CommonsDistributionStagingMojo.java:342)
>  at
> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
>> .buildReadmeAndHeaderHtmlFiles(CommonsDistributionStagingMojo.java:319)
>  at
> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
>> .copyDistributionsIntoScmDirectoryStructure(CommonsDistributionStagingMojo
>> .java:274)
>  at
> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
>> .execute(CommonsDistributionStagingMojo.java:164)
>  at
> org.apache.commons.release.plugin.mojos.CommonsDistributionStagingMojo
>> Test.testSuccess(CommonsDistributionStagingMojoTest.java:77)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(
>> NativeMethodAccessorImpl.java:62)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:498)
>  at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
>> FrameworkMethod.java:50)
>  at
> org.junit.internal.runners.model.ReflectiveCallable.run(
>> ReflectiveCallable.java:12)
>  at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(
>> FrameworkMethod.java:47)
>  at
> org.junit.internal.runners.statements.InvokeMethod.
>> evaluate(InvokeMethod.java:17)
>  at
> org.junit.internal.runners.statements.RunBefores.
>> evaluate(RunBefores.java:26)
>  at
> org.apache.maven.plugin.testing.MojoRule$2.evaluate(MojoRule.java:308)
>  at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>  at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>  at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(
>> BlockJUnit4ClassRunner.java:78)
>  at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(
>> BlockJUnit4ClassRunner.java:57)
>  at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>  at org.junit.runners.ParentRunner$1.schedule(
>> ParentRunner.java:71)
>  at org.junit.runners.ParentRunner.runChildren(
>> ParentRunner.java:288)
>  at org.junit.runners.ParentRunner.access$000(
>> Paren

Re: [release-plugin] Unit test failures

2018-05-29 Thread Gary Gregory 
On Tue, May 29, 2018 at 8:20 AM, Rob Tompkins  wrote:

>
>
> > On May 29, 2018, at 10:16 AM, Gary Gregory 
> wrote:
> >
> >> On Tue, May 29, 2018 at 7:01 AM, Rob Tompkins 
> wrote:
> >>
> >> @Gary - let me know how things run now.
> >>
> >
> > The build passes now with 'mvn clean install site -Danimal.sniffer.skip'
> >
>
> Do you have an opinion on the symbolic links in the distributions svn
> repos?
>

I would keep it simple. For me, saving a few bytes is not worth the added
complication.

Gary


> -Rob
>
> > Thank you,
> > Gary
> >
> >
> >>
>  On May 29, 2018, at 6:01 AM, sebb  wrote:
> 
>  On 29 May 2018 at 02:58, Rob Tompkins  wrote:
>  It looks like this has to do with java setting up symbolic links on a
> >> windows machine. Clearly this is something that we’ll want to overcome,
> but
> >> I’m not certain how to accommodate this. It seems that:
> 
>  Files.createSymbolicLink
> 
>  may not work on Windows. It looks like Apache Storm may have seen this
> >> before with https://issues.apache.org/jira/browse/STORM-1193.
> 
>  Curious if anyone else on the list might have any suggestions here?
> >> Also, I’ll try to dig around in the maven codebases to see if they use
> it
> >> anywhere.
> >>>
> >>> Why should the Commons code set up links at all?
> >>>
>  -Rob
> 
> > On May 28, 2018, at 1:07 PM, Gary Gregory 
> >> wrote:
> >
> > I pulled the latest and I get:
> >
> > [INFO] Preparing to stage distributions
> > [INFO] Checking out dist from: scm:svn:
> > https://dist.apache.org/repos/dist/dev/commons/release-plugin
> > Executing: cmd.exe /X /C "svn --non-interactive checkout
> > https://dist.apache.org/repos/dist/dev/commons/release-plugin
> > C:\vcs\git\apache\commons\commons-release-plugin\target\
> >> testing-commons-release-plugin\scm"
> > Working directory:
> > C:\vcs\git\apache\commons\commons-release-plugin\target\
> >> testing-commons-release-plugin
> > [INFO] Copying RELEASE-NOTES.txt to working directory.
> > [ERROR] Could not build HEADER and README html files
> > java.nio.file.FileSystemException:
> > C:\vcs\git\apache\commons\commons-release-plugin\target\
> >> testing-commons-release-plugin\scm\source\HEADER.html:
> > A required privilege is not held by the client.
> >
> >  at
> > sun.nio.fs.WindowsException.translateToIOException(
> >> WindowsException.java:86)
> >  at
> > sun.nio.fs.WindowsException.rethrowAsIOException(
> >> WindowsException.java:97)
> >  at
> > sun.nio.fs.WindowsException.rethrowAsIOException(
> >> WindowsException.java:102)
> >  at
> > sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(
> >> WindowsFileSystemProvider.java:585)
> >  at java.nio.file.Files.createSymbolicLink(Files.java:1043)
> >  at
> > org.apache.commons.release.plugin.mojos.
> CommonsDistributionStagingMojo
> >> .buildSymbolicLinks(CommonsDistributionStagingMojo.java:342)
> >  at
> > org.apache.commons.release.plugin.mojos.
> CommonsDistributionStagingMojo
> >> .buildReadmeAndHeaderHtmlFiles(CommonsDistributionStagingMojo.java:319)
> >  at
> > org.apache.commons.release.plugin.mojos.
> CommonsDistributionStagingMojo
> >> .copyDistributionsIntoScmDirectoryStructure(
> CommonsDistributionStagingMojo
> >> .java:274)
> >  at
> > org.apache.commons.release.plugin.mojos.
> CommonsDistributionStagingMojo
> >> .execute(CommonsDistributionStagingMojo.java:164)
> >  at
> > org.apache.commons.release.plugin.mojos.
> CommonsDistributionStagingMojo
> >> Test.testSuccess(CommonsDistributionStagingMojoTest.java:77)
> >  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >  at
> > sun.reflect.NativeMethodAccessorImpl.invoke(
> >> NativeMethodAccessorImpl.java:62)
> >  at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> >> DelegatingMethodAccessorImpl.java:43)
> >  at java.lang.reflect.Method.invoke(Method.java:498)
> >  at
> > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
> >> FrameworkMethod.java:50)
> >  at
> > org.junit.internal.runners.model.ReflectiveCallable.run(
> >> ReflectiveCallable.java:12)
> >  at
> > org.junit.runners.model.FrameworkMethod.invokeExplosively(
> >> FrameworkMethod.java:47)
> >  at
> > org.junit.internal.runners.statements.InvokeMethod.
> >> evaluate(InvokeMethod.java:17)
> >  at
> > org.junit.internal.runners.statements.RunBefores.
> >> evaluate(RunBefores.java:26)
> >  at
> > org.apache.maven.plugin.testing.MojoRule$2.evaluate(
> MojoRule.java:308)
> >  at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> >  at org.junit.runners.ParentRunner.runLeaf(
> ParentRunner.java:325)
> >  at
> > org.junit.runners.BlockJUnit4ClassRunner.runChild(
> >> BlockJUnit4ClassRunner.java:78)
> >>>

[release-plugin] TODOs

2018-05-29 Thread Gary Gregory 
Hi Rob and All:

I see the following TODOs before releasing 1.3:

- Commit the site as is to the dist folder so that links in a VOTE email
work (like 'The CLIRR report is here). I am not sure we still need the site
zip. I am not sure we need to make that an option, needs feedback.
- Match the dist path and tag names to match what the vote-txt goal
generates (see
src/main/resources/commons-xdoc-templates/vote-txt-template.txt)

Extra Credit: How do we get the  after a deploy for a URL
https://repository.apache.org/content/repositories/orgapachecommons-/org/apache/commons/@ARTIFACTID@/@VERSION@/

Gary