Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-13 Thread Benedikt Ritter 
Hello,

this vote passes with following votes:

Paul King: +1 (non-binding)
Bruno P. Kinoshita: +1
Robert Scholte: +1 (non-binding)
Oliver Heger: +1
Benedikt Ritter: +1

Thank you to all who have reviewed this RC.

Benedikt

> Am 09.03.2017 um 14:30 schrieb Benedikt Ritter :
> 
> Hi,
> 
> We have fixed some bugs and added two new features since CLI 1.3.1 was 
> released,
> so I would like to release CLI 1.4.
> 
> CLI 1.4 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
> revision 18640)
> 
> The tag is here:
>http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ (svn 
> revision 1786159)
>N.B. the SVN revision is required because SVN tags are not immutable.
> 
> Maven artifacts are here:
>  https://repository.apache.org/content/repositories/orgapachecommons-1240
> 
> These are the Maven Artifacts and their hashes:
> 
> commons-cli-1.4.pom.asc
> (SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
> commons-cli-1.4-test-sources.jar
> (SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
> commons-cli-1.4.jar
> (SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
> commons-cli-1.4-sources.jar.asc
> (SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
> commons-cli-1.4-tests.jar
> (SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
> commons-cli-1.4-tests.jar.asc
> (SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
> commons-cli-1.4-javadoc.jar.asc
> (SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
> commons-cli-1.4-sources.jar
> (SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
> commons-cli-1.4-javadoc.jar
> (SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
> commons-cli-1.4-test-sources.jar.asc
> (SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
> commons-cli-1.4.jar.asc
> (SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
> commons-cli-1.4.pom
> (SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)
> 
> I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
> required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. 
> If anybody has such old JDKs installed, I would appreciate some feedback on 
> this.
> 
> Details of changes since 1.3.1 are in the release notes:
>  
> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
>  http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html
> 
> Site:
>  http://home.apache.org/~britter/commons/cli/1.4-RC1/
>  (note some *relative* links are broken and the 1.4 directories are not yet 
> created - these will be OK once the site is deployed)
> 
> Clirr Report (compared to 1.3.1):
>  http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
> (Sorry, after updating to commons-parent 42 the clirr report was not 
> generated anymore. I had to do it by hand, that’s why it has a different 
> style)
> 
> RAT Report:
>  http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html
> 
> KEYS:
>  https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 13:30 UTC 12-March 2017
> 
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
> 
> Thanks!
> 
> Benedikt
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-13 Thread Benedikt Ritter 

> Am 09.03.2017 um 14:30 schrieb Benedikt Ritter :
> 
> Hi,
> 
> We have fixed some bugs and added two new features since CLI 1.3.1 was 
> released,
> so I would like to release CLI 1.4.
> 
> CLI 1.4 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
> revision 18640)
> 
> The tag is here:
>http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ (svn 
> revision 1786159)
>N.B. the SVN revision is required because SVN tags are not immutable.
> 
> Maven artifacts are here:
>  https://repository.apache.org/content/repositories/orgapachecommons-1240
> 
> These are the Maven Artifacts and their hashes:
> 
> commons-cli-1.4.pom.asc
> (SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
> commons-cli-1.4-test-sources.jar
> (SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
> commons-cli-1.4.jar
> (SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
> commons-cli-1.4-sources.jar.asc
> (SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
> commons-cli-1.4-tests.jar
> (SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
> commons-cli-1.4-tests.jar.asc
> (SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
> commons-cli-1.4-javadoc.jar.asc
> (SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
> commons-cli-1.4-sources.jar
> (SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
> commons-cli-1.4-javadoc.jar
> (SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
> commons-cli-1.4-test-sources.jar.asc
> (SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
> commons-cli-1.4.jar.asc
> (SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
> commons-cli-1.4.pom
> (SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)
> 
> I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
> required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. 
> If anybody has such old JDKs installed, I would appreciate some feedback on 
> this.
> 
> Details of changes since 1.3.1 are in the release notes:
>  
> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
>  http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html
> 
> Site:
>  http://home.apache.org/~britter/commons/cli/1.4-RC1/
>  (note some *relative* links are broken and the 1.4 directories are not yet 
> created - these will be OK once the site is deployed)
> 
> Clirr Report (compared to 1.3.1):
>  http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
> (Sorry, after updating to commons-parent 42 the clirr report was not 
> generated anymore. I had to do it by hand, that’s why it has a different 
> style)
> 
> RAT Report:
>  http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html
> 
> KEYS:
>  https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 13:30 UTC 12-March 2017
> 
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because…

Here is my +1

> 
> Thanks!
> 
> Benedikt
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-11 Thread Oliver Heger 
Hi,

build works fine with Java 1.5 and 1.8 on Windows 10, artifacts and site
look good.

I noticed the following minor things:
- 54 unit tests are skipped which is a high number given the total
number of 372. It may be worth having a look at those and remove
outdated or fix broken ones.
- The Javadoc (opened from both the link below "User Guide" and the
reports section) shows version Commons CLI 1.3 (direct on the index
page); not sure why here an older version appears.

This is not blocking, so +1.

Oliver

Am 09.03.2017 um 14:30 schrieb Benedikt Ritter:
> Hi,
> 
> We have fixed some bugs and added two new features since CLI 1.3.1 was 
> released,
> so I would like to release CLI 1.4.
> 
> CLI 1.4 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
> revision 18640)
> 
> The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ (svn 
> revision 1786159)
> N.B. the SVN revision is required because SVN tags are not immutable.
> 
> Maven artifacts are here:
>   https://repository.apache.org/content/repositories/orgapachecommons-1240
> 
> These are the Maven Artifacts and their hashes:
> 
> commons-cli-1.4.pom.asc
> (SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
> commons-cli-1.4-test-sources.jar
> (SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
> commons-cli-1.4.jar
> (SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
> commons-cli-1.4-sources.jar.asc
> (SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
> commons-cli-1.4-tests.jar
> (SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
> commons-cli-1.4-tests.jar.asc
> (SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
> commons-cli-1.4-javadoc.jar.asc
> (SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
> commons-cli-1.4-sources.jar
> (SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
> commons-cli-1.4-javadoc.jar
> (SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
> commons-cli-1.4-test-sources.jar.asc
> (SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
> commons-cli-1.4.jar.asc
> (SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
> commons-cli-1.4.pom
> (SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)
> 
> I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
> required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. 
> If anybody has such old JDKs installed, I would appreciate some feedback on 
> this.
> 
> Details of changes since 1.3.1 are in the release notes:
>   
> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html
> 
> Site:
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/
>   (note some *relative* links are broken and the 1.4 directories are not yet 
> created - these will be OK once the site is deployed)
> 
> Clirr Report (compared to 1.3.1):
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
> (Sorry, after updating to commons-parent 42 the clirr report was not 
> generated anymore. I had to do it by hand, that’s why it has a different 
> style)
> 
> RAT Report:
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html
> 
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 13:30 UTC 12-March 2017
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> 
> Benedikt
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-11 Thread Robert Scholte 

+1 and thanks for picking this up, really appreciate it.

thanks,
Robert

On Thu, 09 Mar 2017 14:30:28 +0100, Benedikt Ritter   
wrote:



Hi,

We have fixed some bugs and added two new features since CLI 1.3.1 was  
released,

so I would like to release CLI 1.4.

CLI 1.4 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn  
revision 18640)


The tag is here:
http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/  
(svn revision 1786159)

N.B. the SVN revision is required because SVN tags are not immutable.

Maven artifacts are here:
  https://repository.apache.org/content/repositories/orgapachecommons-1240

These are the Maven Artifacts and their hashes:

commons-cli-1.4.pom.asc
(SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
commons-cli-1.4-test-sources.jar
(SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
commons-cli-1.4.jar
(SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
commons-cli-1.4-sources.jar.asc
(SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
commons-cli-1.4-tests.jar
(SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
commons-cli-1.4-tests.jar.asc
(SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
commons-cli-1.4-javadoc.jar.asc
(SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
commons-cli-1.4-sources.jar
(SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
commons-cli-1.4-javadoc.jar
(SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
commons-cli-1.4-test-sources.jar.asc
(SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
commons-cli-1.4.jar.asc
(SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
commons-cli-1.4.pom
(SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)

I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that  
CLI required at least Java 5 and I haven’t tested this release with 1.5  
or 1.6. If anybody has such old JDKs installed, I would appreciate some  
feedback on this.


Details of changes since 1.3.1 are in the release notes:
  
https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
  http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html

Site:
  http://home.apache.org/~britter/commons/cli/1.4-RC1/
  (note some *relative* links are broken and the 1.4 directories are not  
yet created - these will be OK once the site is deployed)


Clirr Report (compared to 1.3.1):
  http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
(Sorry, after updating to commons-parent 42 the clirr report was not  
generated anymore. I had to do it by hand, that’s why it has a different  
style)


RAT Report:
  http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html

KEYS:
  https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now,
i.e. sometime after 13:30 UTC 12-March 2017

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Thanks!

Benedikt




-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-09 Thread Benedikt Ritter 
Hello Paul,

> Am 10.03.2017 um 01:03 schrieb Paul King :
> 
> Oh, I did notice that the README.md still has 1.3.1 rather than 1.4
> when referencing
> how to retrieve the Maven artifact. Is a "mvn commons:readme-md" required?

You’re right, it would be better to have this correct in the release tag. 
However I usually update the README.md after the artifacts have been published, 
because the README.md will directly be visible on GitHub. I don’t want to 
confuse users looking for coordinates on GitHub. Since CLI is still on SVN and 
I don’t do release branches in SVN I have to make all release preparations on 
trunk/master.

Thanks for reviewing!
Benedikt

> 
> On Fri, Mar 10, 2017 at 10:00 AM, Paul King  wrote:
>> +1 (non-binding)
>> I checked md5/sha1/asc for the sources jar and src zip.
>> I ran "mvn test" from the src zip using Java 1.6.0_45 and Maven 3.2.5.
>> I ran Apache Groovy's test suite against 1.4 which runs quite a few
>> tests for CliBuilder (which has commons cli under the covers) as well
>> as numerous other tests where Groovy uses commons cli directly too.
>> 
>> Cheers, Paul.
>> 
>> 
>> On Thu, Mar 9, 2017 at 11:30 PM, Benedikt Ritter  wrote:
>>> Hi,
>>> 
>>> We have fixed some bugs and added two new features since CLI 1.3.1 was 
>>> released,
>>> so I would like to release CLI 1.4.
>>> 
>>> CLI 1.4 RC1 is available for review here:
>>>https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
>>> revision 18640)
>>> 
>>> The tag is here:
>>>http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ 
>>> (svn revision 1786159)
>>>N.B. the SVN revision is required because SVN tags are not immutable.
>>> 
>>> Maven artifacts are here:
>>>  https://repository.apache.org/content/repositories/orgapachecommons-1240
>>> 
>>> These are the Maven Artifacts and their hashes:
>>> 
>>> commons-cli-1.4.pom.asc
>>> (SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
>>> commons-cli-1.4-test-sources.jar
>>> (SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
>>> commons-cli-1.4.jar
>>> (SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
>>> commons-cli-1.4-sources.jar.asc
>>> (SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
>>> commons-cli-1.4-tests.jar
>>> (SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
>>> commons-cli-1.4-tests.jar.asc
>>> (SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
>>> commons-cli-1.4-javadoc.jar.asc
>>> (SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
>>> commons-cli-1.4-sources.jar
>>> (SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
>>> commons-cli-1.4-javadoc.jar
>>> (SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
>>> commons-cli-1.4-test-sources.jar.asc
>>> (SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
>>> commons-cli-1.4.jar.asc
>>> (SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
>>> commons-cli-1.4.pom
>>> (SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)
>>> 
>>> I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that 
>>> CLI required at least Java 5 and I haven’t tested this release with 1.5 or 
>>> 1.6. If anybody has such old JDKs installed, I would appreciate some 
>>> feedback on this.
>>> 
>>> Details of changes since 1.3.1 are in the release notes:
>>>  
>>> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
>>>  http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html
>>> 
>>> Site:
>>>  http://home.apache.org/~britter/commons/cli/1.4-RC1/
>>>  (note some *relative* links are broken and the 1.4 directories are not yet 
>>> created - these will be OK once the site is deployed)
>>> 
>>> Clirr Report (compared to 1.3.1):
>>>  http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
>>> (Sorry, after updating to commons-parent 42 the clirr report was not 
>>> generated anymore. I had to do it by hand, that’s why it has a different 
>>> style)
>>> 
>>> RAT Report:
>>>  http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html
>>> 
>>> KEYS:
>>>  https://www.apache.org/dist/commons/KEYS
>>> 
>>> Please review the release candidate and vote.
>>> This vote will close no sooner that 72 hours from now,
>>> i.e. sometime after 13:30 UTC 12-March 2017
>>> 
>>>  [ ] +1 Release these artifacts
>>>  [ ] +0 OK, but...
>>>  [ ] -0 OK, but really should fix...
>>>  [ ] -1 I oppose this release because...
>>> 
>>> Thanks!
>>> 
>>> Benedikt
>>> 
>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For

Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-09 Thread Bruno P. Kinoshita 
[ X ] +1 Release these artifacts

Builds fine on

Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-64-generic", arch: "amd64", family: "unix"

Site successfully generated too, no outstanding issues in the reports.

Cheers
Bruno




- Original Message -
From: Benedikt Ritter 
To: Commons Developers List 
Cc: Robert Scholte 
Sent: Friday, 10 March 2017 2:30 AM
Subject: [VOTE] Release Apache Commons CLI 1.4 based on RC1

Hi,

We have fixed some bugs and added two new features since CLI 1.3.1 was released,
so I would like to release CLI 1.4.

CLI 1.4 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
revision 18640)

The tag is here:
http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ (svn 
revision 1786159)
N.B. the SVN revision is required because SVN tags are not immutable.

Maven artifacts are here:
  https://repository.apache.org/content/repositories/orgapachecommons-1240

These are the Maven Artifacts and their hashes:

commons-cli-1.4.pom.asc
(SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
commons-cli-1.4-test-sources.jar
(SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
commons-cli-1.4.jar
(SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
commons-cli-1.4-sources.jar.asc
(SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
commons-cli-1.4-tests.jar
(SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
commons-cli-1.4-tests.jar.asc
(SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
commons-cli-1.4-javadoc.jar.asc
(SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
commons-cli-1.4-sources.jar
(SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
commons-cli-1.4-javadoc.jar
(SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
commons-cli-1.4-test-sources.jar.asc
(SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
commons-cli-1.4.jar.asc
(SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
commons-cli-1.4.pom
(SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)

I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. If 
anybody has such old JDKs installed, I would appreciate some feedback on this.

Details of changes since 1.3.1 are in the release notes:
  
https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
  http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html

Site:
  http://home.apache.org/~britter/commons/cli/1.4-RC1/
  (note some *relative* links are broken and the 1.4 directories are not yet 
created - these will be OK once the site is deployed)

Clirr Report (compared to 1.3.1):
  http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
(Sorry, after updating to commons-parent 42 the clirr report was not generated 
anymore. I had to do it by hand, that’s why it has a different style)

RAT Report:
  http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html

KEYS:
  https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now,
i.e. sometime after 13:30 UTC 12-March 2017

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Thanks!

Benedikt




-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-09 Thread Paul King 
Oh, I did notice that the README.md still has 1.3.1 rather than 1.4
when referencing
how to retrieve the Maven artifact. Is a "mvn commons:readme-md" required?

On Fri, Mar 10, 2017 at 10:00 AM, Paul King  wrote:
> +1 (non-binding)
> I checked md5/sha1/asc for the sources jar and src zip.
> I ran "mvn test" from the src zip using Java 1.6.0_45 and Maven 3.2.5.
> I ran Apache Groovy's test suite against 1.4 which runs quite a few
> tests for CliBuilder (which has commons cli under the covers) as well
> as numerous other tests where Groovy uses commons cli directly too.
>
> Cheers, Paul.
>
>
> On Thu, Mar 9, 2017 at 11:30 PM, Benedikt Ritter  wrote:
>> Hi,
>>
>> We have fixed some bugs and added two new features since CLI 1.3.1 was 
>> released,
>> so I would like to release CLI 1.4.
>>
>> CLI 1.4 RC1 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
>> revision 18640)
>>
>> The tag is here:
>> http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ 
>> (svn revision 1786159)
>> N.B. the SVN revision is required because SVN tags are not immutable.
>>
>> Maven artifacts are here:
>>   https://repository.apache.org/content/repositories/orgapachecommons-1240
>>
>> These are the Maven Artifacts and their hashes:
>>
>> commons-cli-1.4.pom.asc
>> (SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
>> commons-cli-1.4-test-sources.jar
>> (SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
>> commons-cli-1.4.jar
>> (SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
>> commons-cli-1.4-sources.jar.asc
>> (SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
>> commons-cli-1.4-tests.jar
>> (SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
>> commons-cli-1.4-tests.jar.asc
>> (SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
>> commons-cli-1.4-javadoc.jar.asc
>> (SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
>> commons-cli-1.4-sources.jar
>> (SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
>> commons-cli-1.4-javadoc.jar
>> (SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
>> commons-cli-1.4-test-sources.jar.asc
>> (SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
>> commons-cli-1.4.jar.asc
>> (SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
>> commons-cli-1.4.pom
>> (SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)
>>
>> I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
>> required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. 
>> If anybody has such old JDKs installed, I would appreciate some feedback on 
>> this.
>>
>> Details of changes since 1.3.1 are in the release notes:
>>   
>> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
>>   http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html
>>
>> Site:
>>   http://home.apache.org/~britter/commons/cli/1.4-RC1/
>>   (note some *relative* links are broken and the 1.4 directories are not yet 
>> created - these will be OK once the site is deployed)
>>
>> Clirr Report (compared to 1.3.1):
>>   http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
>> (Sorry, after updating to commons-parent 42 the clirr report was not 
>> generated anymore. I had to do it by hand, that’s why it has a different 
>> style)
>>
>> RAT Report:
>>   http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html
>>
>> KEYS:
>>   https://www.apache.org/dist/commons/KEYS
>>
>> Please review the release candidate and vote.
>> This vote will close no sooner that 72 hours from now,
>> i.e. sometime after 13:30 UTC 12-March 2017
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>> Thanks!
>>
>> Benedikt
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-09 Thread Paul King 
+1 (non-binding)
I checked md5/sha1/asc for the sources jar and src zip.
I ran "mvn test" from the src zip using Java 1.6.0_45 and Maven 3.2.5.
I ran Apache Groovy's test suite against 1.4 which runs quite a few
tests for CliBuilder (which has commons cli under the covers) as well
as numerous other tests where Groovy uses commons cli directly too.

Cheers, Paul.


On Thu, Mar 9, 2017 at 11:30 PM, Benedikt Ritter  wrote:
> Hi,
>
> We have fixed some bugs and added two new features since CLI 1.3.1 was 
> released,
> so I would like to release CLI 1.4.
>
> CLI 1.4 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
> revision 18640)
>
> The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ (svn 
> revision 1786159)
> N.B. the SVN revision is required because SVN tags are not immutable.
>
> Maven artifacts are here:
>   https://repository.apache.org/content/repositories/orgapachecommons-1240
>
> These are the Maven Artifacts and their hashes:
>
> commons-cli-1.4.pom.asc
> (SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
> commons-cli-1.4-test-sources.jar
> (SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
> commons-cli-1.4.jar
> (SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
> commons-cli-1.4-sources.jar.asc
> (SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
> commons-cli-1.4-tests.jar
> (SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
> commons-cli-1.4-tests.jar.asc
> (SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
> commons-cli-1.4-javadoc.jar.asc
> (SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
> commons-cli-1.4-sources.jar
> (SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
> commons-cli-1.4-javadoc.jar
> (SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
> commons-cli-1.4-test-sources.jar.asc
> (SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
> commons-cli-1.4.jar.asc
> (SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
> commons-cli-1.4.pom
> (SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)
>
> I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
> required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. 
> If anybody has such old JDKs installed, I would appreciate some feedback on 
> this.
>
> Details of changes since 1.3.1 are in the release notes:
>   
> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html
>
> Site:
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/
>   (note some *relative* links are broken and the 1.4 directories are not yet 
> created - these will be OK once the site is deployed)
>
> Clirr Report (compared to 1.3.1):
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
> (Sorry, after updating to commons-parent 42 the clirr report was not 
> generated anymore. I had to do it by hand, that’s why it has a different 
> style)
>
> RAT Report:
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 13:30 UTC 12-March 2017
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thanks!
>
> Benedikt
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org