Re: [VOTE] Release JEXL 3.0 based on RC2

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. Artifacts and
site look good.

There are many findbugs and a bunch of PMD warnings, but this is not
blocking.

+1

Oliver

Am 18.12.2015 um 17:05 schrieb Emmanuel Bourg:
> Hi all,
> 
> JEXL 3.0 RC2 is now available for review.
> 
> Distribution: https://dist.apache.org/repos/dist/dev/commons/jexl/
> (r11664)
> 
> Maven artifacts: 
> https://repository.apache.org/content/repositories/orgapachecommons-1133/org/apache/commons/commons-jexl3/3.0/
>
>  Release notes: 
> https://dist.apache.org/repos/dist/dev/commons/jexl/RELEASE-NOTES.txt
>
> 
http://people.apache.org/~ebourg/jexl/site/changes-report.html
> 
> Tag: 
> http://svn.apache.org/repos/asf/commons/proper/jexl/tags/COMMONS_JEXL_3_0-RC2/
> (r1720787)
> 
> Site: http://people.apache.org/~ebourg/jexl/site
> 
> 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. after Mon, 21 Dec 2015
> 16:05:00 GMT
> 
> [ ] +1 Release these artifacts [ ] +0 OK, but... [ ] -0 OK, but
> really should fix... [ ] -1 I oppose this release because...
> 
> Thanks you,
> 
> Emmanuel Bourg
> 

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

Re: [VOTE] Release Apache Commons Weaver 1.2 based on RC1

[Oliver Heger]

Hi Matt,

Am 18.12.2015 um 22:03 schrieb Matt Benson:
> On Fri, Dec 18, 2015 at 2:54 PM, Oliver Heger
> <oliver.he...@oliver-heger.de> wrote:
>> Artifacts and site look good, signatures are fine.
>>
>> However, I was not able to build from source with Java 1.6 and 1.7 on
>> Windows 10. This is what I get:
>>
>> [INFO] --- maven-bundle-plugin:2.5.3:manifest (bundle-manifest) @
>> commons-weaver-maven-plugin ---
>> [ERROR] Manifest
>> org.apache.commons:commons-weaver-maven-plugin:maven-plugin:1.2 : The
>> default package '.' is not permitted by the Import-Package syntax.
>>  This can be caused by compile errors in Eclipse because Eclipse creates
>> valid class files regardless of compile errors.
>> The following package(s) import from the default package null
>> [ERROR] Error(s) found in manifest configuration
>>
>> I am using Maven 3.2.1.
> 
> I had this problem with Java 6, which is why Java 6 was glaringly
> omitted from my "tested with" list. I have no idea what reason there
> would be that the bundle-plugin fails on Java 6 and succeeds on Java
> 7. I am very surprised that you would have had an issue with Java 7,
> however. Can you confirm, Oliver?

yes indeed, I see this error with all Java versions I have tested: from
1.6 to 1.8.

The maven-bundle-plugin does not have a version assigned to it in the
pom. Could this be a problem, that I use a different version than you?

Oliver

> 
> Thanks,
> Matt
> 
>>
>> Oliver
>>
>> Am 17.12.2015 um 23:57 schrieb Matt Benson:
>>> I would like to release the [weaver] component.
>>>
>>> Apache Commons Weaver 1.2 RC1 is available for review at:
>>>   https://dist.apache.org/repos/dist/dev/commons/weaver/ (r11649).
>>>
>>> Maven artifacts are at:
>>>   https://repository.apache.org/content/repositories/orgapachecommons-1132 .
>>>
>>> Tested with Oracle JDKs 7 and 8; IBM JDK 7.
>>>
>>> The Subversion tag is:
>>>   http://svn.apache.org/repos/asf/commons/proper/weaver/tags/1.2_RC1/
>>> (r1720616).
>>>
>>> Site (note some links may be broken; this will be fixed when the site
>>> is deployed):
>>>   http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/index.html
>>>
>>> RAT Report:
>>>   http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/rat-report.html
>>>
>>> Quality Reports (CLIRR/PMD/Checkstyle/Findbugs):
>>>   
>>> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-processor/project-reports.html
>>>   
>>> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html
>>>   
>>> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html
>>>   
>>> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-normalizer/project-reports.html
>>>   
>>> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html
>>>   
>>> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-antlib/project-reports.html
>>>
>>> Keys: https://dist.apache.org/repos/dist/release/commons/KEYS
>>>
>>> Please review the release candidate and vote.
>>>   This vote will close no sooner than 72 hours from now, i.e. after
>>> 2300UTC 20-December 2015
>>>
>>>   [ ] +1 Release these artifacts
>>>   [ ] +0 OK, but...
>>>   [ ] -0 OK, but really should fix...
>>>   [ ] -1 I oppose this release because...
>>>
>>>   Thanks!
>>>
>>> -
>>> 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 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 Weaver 1.2 based on RC1

[Oliver Heger]

Artifacts and site look good, signatures are fine.

However, I was not able to build from source with Java 1.6 and 1.7 on
Windows 10. This is what I get:

[INFO] --- maven-bundle-plugin:2.5.3:manifest (bundle-manifest) @
commons-weaver-maven-plugin ---
[ERROR] Manifest
org.apache.commons:commons-weaver-maven-plugin:maven-plugin:1.2 : The
default package '.' is not permitted by the Import-Package syntax.
 This can be caused by compile errors in Eclipse because Eclipse creates
valid class files regardless of compile errors.
The following package(s) import from the default package null
[ERROR] Error(s) found in manifest configuration

I am using Maven 3.2.1.

Oliver

Am 17.12.2015 um 23:57 schrieb Matt Benson:
> I would like to release the [weaver] component.
> 
> Apache Commons Weaver 1.2 RC1 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/weaver/ (r11649).
> 
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1132 .
> 
> Tested with Oracle JDKs 7 and 8; IBM JDK 7.
> 
> The Subversion tag is:
>   http://svn.apache.org/repos/asf/commons/proper/weaver/tags/1.2_RC1/
> (r1720616).
> 
> Site (note some links may be broken; this will be fixed when the site
> is deployed):
>   http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/index.html
> 
> RAT Report:
>   http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/rat-report.html
> 
> Quality Reports (CLIRR/PMD/Checkstyle/Findbugs):
>   
> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-processor/project-reports.html
>   
> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html
>   
> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html
>   
> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-normalizer/project-reports.html
>   
> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html
>   
> http://people.apache.org/~mbenson/commons-weaver-1.2-rc1/commons-weaver-parent/commons-weaver-antlib/project-reports.html
> 
> Keys: https://dist.apache.org/repos/dist/release/commons/KEYS
> 
> Please review the release candidate and vote.
>   This vote will close no sooner than 72 hours from now, i.e. after
> 2300UTC 20-December 2015
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
> -
> 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 commons-io 2.5 based on RC1

[Oliver Heger]

Hi Kristian,

while checking the release I found some problems:

* The commons-io-2.5.jar in the binary distribution contains a
cobertura.properties file. This is probably created by running the site
build over the release build before creating the distributions. In the
past we had a problematic release because Cobertura seems to mess up
some classes. I cannot remember the exact details, but the jar was not
working correctly. Could this be the case here, too?
* The copyright year in NOTICE is still 2014. I think this is blocking.
* Building with Java 1.6 on Windows 10 gives a test failure:

---
Test set: org.apache.commons.io.FileUtilsTestCase
---
Tests run: 134, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.203
sec <<< FAILURE! - in org.apache.commons.io.FileUtilsTestCase
testGetFile(org.apache.commons.io.FileUtilsTestCase)  Time elapsed: 0
sec  <<< ERROR!
java.io.IOException: Cannot create file
C:\data\dev\projects\OpenSource\io\commons-io-2.5-src\test\io\file1-test.txt
as the parent directory does not exist
at
org.apache.commons.io.testtools.FileBasedTestCase.createFile(FileBasedTestCase.java:60)
at
org.apache.commons.io.FileUtilsTestCase.setUp(FileUtilsTestCase.java:101)

With Java 1.8 it is worse; here I get 71 errors which are mostly similar
to the one before (all in FileUtilsTestCase).

The site looks okay except for the JIRA report which is missing.

-1

Sorry
Oliver


Am 23.11.2015 um 18:31 schrieb Kristian Rosenvold:
>   We have fixed quite a few bugs and added some significant
> enhancements since commons-io was released,
>   so I would like to release commons-io 2.5
> 
>   Foo 2.5 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/io/ (svn revision 11266)
> 
>   Maven artifacts are here:
>https://repository.apache.org/content/repositories/orgapachecommons-1123
> 
>   Details of changes since 2.4 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/io/RELEASE-NOTES.txt
> 
> http://people.apache.org/~krosenvold/commons-io-2.5-RC1/changes-report.html
> 
>   I have tested this with JDK 1.6, 1.7 and 1.8.
> 
>   The tag is here:
> https://svn.apache.org/repos/asf/commons/proper/io/tags/commons-io-2.5-RC1
> (r1715890)
> 
>   Site:
>  http://people.apache.org/~krosenvold/commons-io-2.5-RC1/
>   (note some *relative* links are broken and the 2.5 directories are
>   not yet created - these will be OK once the site is deployed)
> 
>   Clirr Report (compared to 2.4):
>  http://people.apache.org/~krosenvold/commons-io-2.5-RC1/clirr-report.html
> 
> 
>   RAT Report:
>  http://people.apache.org/~krosenvold/commons-io-2.5-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. after
> 19:00 CET 26-March 2015
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
> 
> Kristian
> 
> -
> 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 Commons Collections 4.1 Based on RC2 (24h vote)

[Oliver Heger]

Hi Thomas,

+1

Many thanks
Oliver

Am 25.11.2015 um 23:20 schrieb Thomas Neidhart:
> Hi all,
> 
> we have accumulated enough changes since the last 4.0 release as well as
> we need to provide a fix for the known remote code exploit via java
> de-serialization. Therefore, I would like to start a vote to release
> Commons Collections 4.1 based on RC2.
> 
> Note:
> 
>  * The fix for the security related issue results in Clirr errors as
>unsafe classes in the functor package do not implement the
>Serializable interface anymore. This is mentioned in the release
>notes.
> 
>  * There are 2 test failures with the IBM 6 JDK. The same failures were
>reported for the 4.0 release and are related to a buggy Map
>implementation in this JDK
> 
>  * Commons Collections 4.X does not successfully compile with JDK 9 EA
>This will be tackled in a later release.
> 
> Changes since RC1:
> 
>  * fixed compilation problems of test classes with some Java 8 compilers
>  * fixed some javadoc in IterableUtils and MultiValuedMap
>  * added travis configuration (only in the repository, not part of the
>release) to help a RM by building with different jdks
> 
> Collections 4.1 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/collections/
> (svn revision 11307)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1129/org/apache/commons/commons-collections4/4.1/
> 
> Details of changes since 4.0 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/collections/RELEASE-NOTES.txt
> 
> http://people.apache.org/builds/commons/collections/4.1/RC2/changes-report.html
> 
> The tag is here:
> 
> https://svn.apache.org/repos/asf/commons/proper/collections/tags/COLLECTIONS_4_1_RC2
> (svn revision 1716550)
> 
> Site:
> http://people.apache.org/builds/commons/collections/4.1/RC2/
> 
> Clirr Report (compared to 4.0):
> 
> http://people.apache.org/builds/commons/collections/4.1/RC2/clirr-report.html
> 
> RAT Report:
> 
> http://people.apache.org/builds/commons/collections/4.1/RC2/rat-report.html
> 
> KEYS:
> https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> 
> This vote will close no sooner than 24 hours from now, i.e. after 2400
> GMT 26-November 2015
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks,
> 
> Thomas
> 
> -
> 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 Validator 1.5.0 based on RC1

[Oliver Heger]

Environment:
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T18:37:52+01:00)
Maven home: C:\data\dev\tools\apache-maven-3.2.1\bin\..
Java version: 1.8.0_45, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_45\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos"
(actually, it's Windows 10)

Build works fine, artifacts and site look good.

* I was not able to build the site due to Javadoc failures.
* I wanted to test the ant build, but it seemed pretty difficult to come
to a working setup based on the sample properties. There are components
that ship sample properties which reference the local Maven repo and are
much easier to use. Maybe drop the ant build completely?
* There are some Checkstyle and Findbugs errors, but they do not appear
to be too critical. Maybe the one about "Inconsistent synchronization of
org.apache.commons.validator.ValidatorAction.jsFunction" could need some
investigation?

No blockers, so +1

Oliver

Am 19.11.2015 um 10:48 schrieb sebb:
> It's probably about time to release VALIDATOR.
> There have been quite a few improvements and fixes since the last version.
> 
> ==
> 
> Validator 1.5.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/validator/ (svn
> revision 11236)
> 
> ./binaries/commons-validator-1.5.0-bin.tar.gz.sha1:d1ec43eee78475675787db4ce478f03e9089a38f
> ./binaries/commons-validator-1.5.0-bin.zip.sha1:de3664516fdf68667d10b8d060eebd0cf1e349c5
> ./source/commons-validator-1.5.0-src.tar.gz.sha1:737f4df692f3d64bd8c0c6ba6c39e1a7533309c0
> ./source/commons-validator-1.5.0-src.zip.sha1:690c353b52359e75a6b5f0bd1b0cf0f34067c544
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1118/commons-validator/commons-validator/1.5.0/
> 
> These are the artifacts and their hashes
> 
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-tests.jar
> (SHA1: 371f755d033b4a5d4a8b799e453e27e8211179a7)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0.pom
> (SHA1: 4050c881a79cd5e621339c749ef03b47eb851a4a)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0.jar
> (SHA1: 26b98c21975c5caf6bf34bacdeb7183be7a65970)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-javadoc.jar
> (SHA1: f3f3364cb4b3e9d9b0362b2bb2770a579ec76a64)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-sources.jar
> (SHA1: 96c77b61d4ed9ca3b58a7a40bac7fa98a09f5c2f)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-test-sources.jar
> (SHA1: 68e7c52affe4fdc98d4431e6b9ffcc30969279a1)
> 
>   Details of changes since 1.4.1 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/validator/RELEASE-NOTES.txt
> http://people.apache.org/~sebb/validator-1.5.0-RC1/changes-report.html
> 
>   I have tested this with JDK 1.6, 1.7, 1.8 using maven3.
> 
>   The tag is here:
> 
> http://svn.apache.org/repos/asf/commons/proper/validator/tags/VALIDATOR_1_5_0_RC1/
> (svn 1715135)
>   N.B. the SVN revision is required because SVN tags are not immutable.
> 
>   Site:
> http://people.apache.org/~sebb/validator-1.5.0-RC1/
>   (note some *relative* links are broken and the 1.5.0 directories are
>   not yet created - these will be OK once the site is deployed)
> 
>   Clirr Report (compared to 1.4.1):
> http://people.apache.org/~sebb/validator-1.5.0-RC1/clirr-report.html
> 
>   RAT Report:
> http://people.apache.org/~sebb/validator-1.5.0-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. after
> 10:00 GMT 22-Nov 2015
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
>   Sebb
> 
> -
> 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 NET 3.4 based on RC2 - resend with corrected tag

[Oliver Heger]

Build works fine for me with Java 1.5 and Java 1.8 on Windows 10.
Artifacts and site look good. So +1.

Interestingly, when I build the site locally my clirr report shows 12
errors. In addition to the 3 errors about methods added to an interface,
I also get a bunch of errors about public methods which are now final,
for instance:

* public org.apache.commons.net.ftp.FTPCmd[] values()
* public org.apache.commons.net.imap.IMAP$IMAPState[] values()
* public org.apache.commons.net.imap.IMAPClient$SEARCH_CRITERIA[] values()

These are all enum classes, so the message is pretty pointless. Maybe a
Java 8 issue?

Oliver

Am 22.11.2015 um 16:58 schrieb sebb:
> It's probably about time to release NET.
> There have been quite a few improvements and fixes since the last version.
> 
> [This is a repeat of the original mail, but using a tag that actually
> exists this time]
> 
> ==
> 
> Net 3.4 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/net/ (svn revision 11241)
> 
> ./binaries/commons-net-3.4-bin.tar.gz.sha1:88411522395b4000b038a94ab007be89ebda2ec3
> ./binaries/commons-net-3.4-bin.zip.sha1:f252a45b1610346116c9dd966fec9a15171223d1
> ./source/commons-net-3.4-src.tar.gz.sha1:abfba84427a06341e113d59d8f75855e67093087
> ./source/commons-net-3.4-src.zip.sha1:f3b38dfcccd8fcdc9ac500a5f8580a19817b
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1120/commons-net/commons-net/3.4/
> 
> These are the artifacts and their hashes
> 
> /commons-net/commons-net/3.4/commons-net-3.4-test-sources.jar
> (SHA1: fdb74119054a2aacc134c56137660d7a0a40e4a8)
> /commons-net/commons-net/3.4/commons-net-3.4-javadoc.jar
> (SHA1: b882750c8dbd480e2b9afd357dcf71d962f2fa03)
> /commons-net/commons-net/3.4/commons-net-3.4-ftp.jar
> (SHA1: 6fc585e5f3dc8333b20110af22a8bae59f5246cb)
> /commons-net/commons-net/3.4/commons-net-3.4-tests.jar
> (SHA1: ce44ebc0e7be56c3bd650700be93c5b377b47573)
> /commons-net/commons-net/3.4/commons-net-3.4.pom
> (SHA1: d1790447a41c848af8cba0919fae7a577fbc744a)
> /commons-net/commons-net/3.4/commons-net-3.4.jar
> (SHA1: 5e984db9554728564d58e90da5d90eff8ae8cf2d)
> /commons-net/commons-net/3.4/commons-net-3.4-sources.jar
> (SHA1: 08439b8f20d7bdec502423732798a639501732c8)
> /commons-net/commons-net/3.4/commons-net-3.4-examples.jar
> (SHA1: 33abb13d790501fc9e4e77a40425bc381d39b9ca)
> 
>   Details of changes since 3.3 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/net/RELEASE-NOTES.txt
> http://people.apache.org/~sebb/net-3.4-RC2/changes-report.html
> 
>   I have tested this with JDK 1.6, 1.7, 1.8 using maven3.
> 
>   The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_4_RC2/
> (svn 1715635)
> 
>   N.B. the SVN revision is required because SVN tags are not immutable.
> 
>   Site:
> http://people.apache.org/~sebb/net-3.4-RC2/
>   (note some *relative* links are broken and the 3.4 directories are
>   not yet created - these will be OK once the site is deployed)
> 
>   download_net.cgi does not work, but the template can be checked at
> http://people.apache.org/~sebb/net-3.4-RC2/download_net.html
> 
>   Clirr Report (compared to 3.3):
> http://people.apache.org/~sebb/net-3.4-RC2/clirr-report.html
> 
>   Note that adding methods to an interface is binary-compatible, but
> not source-compatible
>   This change is documented in the Release Notes
> 
>   RAT Report:
> http://people.apache.org/~sebb/net-3.4-RC2/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. after
> 14:00 GMT 22-Nov 2015
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
>   Sebb
> 
> -
> 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 Commons Collections 4.1 Based on RC1

[Oliver Heger]

The Maven build worked fine with Java 1.6 and 1.7 on Windows 10. With
Java 1.8 I get the following compilation error in test classes:

[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/c:/data/dev/projects/OpenSource/collections/commons-collections4-4.1-src/src/test/java/org/apache/commons/collections4/FluentIterableTest.java:[242,41]
reference to forEach is ambiguous
  both method forEach(java.util.function.Consumer) in
java.lang.Iterable and method
forEach(org.apache.commons.collections4.Closure) in
org.apache.commons.collections4.FluentIterable match
[INFO] 1 error

Artifacts and site look good. As the compilation error is only in a test
class, this is not blocking.

+1

Oliver

Am 22.11.2015 um 23:26 schrieb Thomas Neidhart:
> Hi all,
> 
> we have accumulated enough changes since the last 4.0 release as well as
> we need to provide a fix for the known remote code exploit via java
> de-serialization. Therefore, I would like to start a vote to release
> Commons Collections 4.1 based on RC1.
> 
> Note:
> 
> The fix for the security related issue results in Clirr errors as unsafe
> classes in the functor package do not implement the Serializable
> interface anymore. This is mentioned in the release notes.
> 
> 
> Collections 4.1 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/collections/
> (svn revision 11263)
> 
> Maven artifacts are here:
> 
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1122/org/apache/commons/commons-collections4/4.1/
> 
> Details of changes since 4.0 are in the release notes:
> 
> 
> https://dist.apache.org/repos/dist/dev/commons/collections/RELEASE-NOTES.txt
> 
> 
> http://people.apache.org/builds/commons/collections/4.1/RC1/changes-report.html
> 
> The tag is here:
> 
> 
> https://svn.apache.org/repos/asf/commons/proper/collections/tags/COLLECTIONS_4_1_RC1
> (svn revision 1715703)
> 
> Site:
> http://people.apache.org/builds/commons/collections/4.1/RC1/
> 
> Clirr Report (compared to 4.0):
> 
> 
> http://people.apache.org/builds/commons/collections/4.1/RC1/clirr-report.html
> 
> RAT Report:
> 
> 
> http://people.apache.org/builds/commons/collections/4.1/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. after 2400
> GMT 25-November 2015
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks,
> 
> Thomas
> 
> -
> 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: [beanutils] release 1.9.3?

[Oliver Heger]

Am 01.06.2016 um 22:09 schrieb Gary Gregory:
> On Wed, Jun 1, 2016 at 12:46 PM, Oliver Heger <oliver.he...@oliver-heger.de>
> wrote:
> 
>>
>>
>> Am 31.05.2016 um 23:31 schrieb Gary Gregory:
>>> While there is not much new for 1.9.3, just two fixes, I would not mind
>>> pushing out a release, just to get the refreshed dependency on Commons
>>> Collection out since there has been noise about it related to security.
>>>
>>> Thoughts?
>>
>> +1, would it be possible to fix BEANUTILS-477? This came up already
>> multiple times. It is probably only suppressing some log output.
>>
>> I am currently pretty busy, otherwise I would look into it myself.
>>
> 
> Well, we can RERO and do a 1.9.4 and get to it when you can dig in.

Changed priorities and fixed it.

Oliver

> 
> Gary
> 
> 
>> Thanks
>> Oliver
>>
>>>
>>> Gary
>>>
>>
>> -
>> 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] Apache Commons BeanUtils 1.9.3 RC1

[Oliver Heger]

Am 03.06.2016 um 22:16 schrieb Gary Gregory:
> On Jun 3, 2016 12:53 PM, "Oliver Heger" <oliver.he...@oliver-heger.de>
> wrote:
>>
>> Build works fine with Java 1.6 on Windows 10. Artifacts and site look
> good.
>>
>> The site cannot be built with Java 8, and the release notes are missing
>> BEANUTILS-477, but this is not blocking.
>>
>> I ran the tests for [configuration] with the new jar and got a single
>> test failure which seems to be caused by the change for BEANUTILS-474.
>> The tests sets a property using the method setIOFactory() and assumes
>> that the property name is iOFactory. However, now the name IOFactory
>> (with capital I) is returned. Is this correct/desired?
> 
> Yes, based on the description of the ticket that deals with the cap change
> IIRC, on my phone now, I can check details later but I think this change is
> indeed as desired.
> 
> Maybe the test is
>> just wrong, but in the worst case this change could break some
>> configuration files. How should we handle this?
> 
> The test should be adjusted IMO.
> 
> A more conservative path would be to revert the change and roll a new RC
> based on the desire for 100% behavior compatibility if that is what we want.

I also tend to agree that the test should be adapted. It is very
unlikely that somebody declares an IOFactory in a configuration file.
And most other properties should have uncritical names. So the risk to
break something is pretty low.

Oliver

> 
> Gary
> 
>>
>> Oliver
>>
>> Am 03.06.2016 um 02:24 schrieb Gary Gregory:
>>> Apache Commons BeanUtils 1.9.3 RC1 is available for review here:
>>>
>>> https://dist.apache.org/repos/dist/dev/commons/beanutils/
>>> (revision 13874)
>>>
>>> commons-beanutils-1.9.3-bin.tar.gz
>>> (SHA1: 5c66783bb2bce21992cc3515a7b78f36f17c8709)
>>> commons-beanutils-1.9.3-bin.zip
>>> (SHA1: 3508ced3e244bc1583f6f4be119f50fe4fd162b3)
>>> commons-beanutils-1.9.3-src.tar.gz
>>> (SHA1: 51879c555ae045f2c09a24eb69a68b6af0544c06)
>>> commons-beanutils-1.9.3-src.zip
>>> (SHA1: 0a16325c44dfee1a29e1e6788115930acbb13313)
>>>
>>> Maven artifacts are here:
>>>
>>>
> https://repository.apache.org/content/repositories/orgapachecommons-1176/commons-beanutils/commons-beanutils/1.9.3/
>>>
>>> These are the artifacts and their hashes:
>>>
>>> commons-beanutils-1.9.3-test-sources.jar
>>> (SHA1: 5365ebf268504d69941c21007a2c0a1334589e8f)
>>> commons-beanutils-1.9.3-sources.jar
>>> (SHA1: 53bae8809672897cb9954669775fb214623c6b89)
>>> commons-beanutils-1.9.3.pom
>>> (SHA1: dbedbbc25b2a981a7598f647100092ce5cb28a55)
>>> commons-beanutils-1.9.3.jar
>>> (SHA1: 15f7207f3ccfb6aa607eb93414723bf8a0c9297c)
>>> commons-beanutils-1.9.3-javadoc.jar
>>> (SHA1:71f2729e5b5bc5f969233c190c105607f55859bf)
>>> commons-beanutils-1.9.3-tests.jar
>>> (SHA1: 3c0a8818f23da165b6e825874c3287e1cbec403b)
>>>
>>> Details of changes since 1.9.2 are in the release notes:
>>>
>>>
> https://dist.apache.org/repos/dist/dev/commons/beanutils/RELEASE-NOTES.txttxt
>>>
> http://home.apache.org/~ggregory/beanutils-1.9.3-rc1/site/changes-report.html
>>>
>>>
>>> The tag is here:
>>>
> https://svn.apache.org/repos/asf/commons/proper/beanutils/tags/beanutils-1.9.3-RC1/
>>> (revision 1745420)
>>>
>>> Site:
>>> http://home.apache.org/~ggregory/beanutils-1.9.3-rc1/site/
>>>
>>> (some *relative* links are broken - these will be OK once the site
>>> is deployed)
>>>
>>> Clirr Report (compared to 1.9.2):
>>>
> http://home.apache.org/~ggregory/beanutils-1.9.3-rc1/site/clirr-report.html
>>>
>>> RAT Report:
>>>
> http://home.apache.org/~ggregory/beanutils-1.9.3-rc1/site/rat-report.html
>>>
>>> KEYS:
>>> https://www.apache.org/dist/commons/KEYS
>>>
>>> Please review the release candidate and vote.
>>>
>>> This vote will close no sooner than 72 hours from now, i.e. sometime
> after
>>> 18:00 PST 5 June 2016
>>>
>>>
>>> [ ] +1 Release these artifacts
>>> [ ] +0 OK, but...
>>> [ ] -0 OK, but really should fix...
>>> [ ] -1 I oppose this release because...
>>>
>>> Thanks!
>>> Gary Gregory
>>>
>>>
>>
>> -
>> 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] Apache Commons BeanUtils 1.9.3 RC1

[Oliver Heger]

Build works fine with Java 1.6 on Windows 10. Artifacts and site look good.

The site cannot be built with Java 8, and the release notes are missing
BEANUTILS-477, but this is not blocking.

I ran the tests for [configuration] with the new jar and got a single
test failure which seems to be caused by the change for BEANUTILS-474.
The tests sets a property using the method setIOFactory() and assumes
that the property name is iOFactory. However, now the name IOFactory
(with capital I) is returned. Is this correct/desired? Maybe the test is
just wrong, but in the worst case this change could break some
configuration files. How should we handle this?

Oliver

Am 03.06.2016 um 02:24 schrieb Gary Gregory:
> Apache Commons BeanUtils 1.9.3 RC1 is available for review here:
> 
> https://dist.apache.org/repos/dist/dev/commons/beanutils/
> (revision 13874)
> 
> commons-beanutils-1.9.3-bin.tar.gz
> (SHA1: 5c66783bb2bce21992cc3515a7b78f36f17c8709)
> commons-beanutils-1.9.3-bin.zip
> (SHA1: 3508ced3e244bc1583f6f4be119f50fe4fd162b3)
> commons-beanutils-1.9.3-src.tar.gz
> (SHA1: 51879c555ae045f2c09a24eb69a68b6af0544c06)
> commons-beanutils-1.9.3-src.zip
> (SHA1: 0a16325c44dfee1a29e1e6788115930acbb13313)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1176/commons-beanutils/commons-beanutils/1.9.3/
> 
> These are the artifacts and their hashes:
> 
> commons-beanutils-1.9.3-test-sources.jar
> (SHA1: 5365ebf268504d69941c21007a2c0a1334589e8f)
> commons-beanutils-1.9.3-sources.jar
> (SHA1: 53bae8809672897cb9954669775fb214623c6b89)
> commons-beanutils-1.9.3.pom
> (SHA1: dbedbbc25b2a981a7598f647100092ce5cb28a55)
> commons-beanutils-1.9.3.jar
> (SHA1: 15f7207f3ccfb6aa607eb93414723bf8a0c9297c)
> commons-beanutils-1.9.3-javadoc.jar
> (SHA1:71f2729e5b5bc5f969233c190c105607f55859bf)
> commons-beanutils-1.9.3-tests.jar
> (SHA1: 3c0a8818f23da165b6e825874c3287e1cbec403b)
> 
> Details of changes since 1.9.2 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/beanutils/RELEASE-NOTES.txttxt
> http://home.apache.org/~ggregory/beanutils-1.9.3-rc1/site/changes-report.html
> 
> 
> The tag is here:
> https://svn.apache.org/repos/asf/commons/proper/beanutils/tags/beanutils-1.9.3-RC1/
> (revision 1745420)
> 
> Site:
> http://home.apache.org/~ggregory/beanutils-1.9.3-rc1/site/
> 
> (some *relative* links are broken - these will be OK once the site
> is deployed)
> 
> Clirr Report (compared to 1.9.2):
> http://home.apache.org/~ggregory/beanutils-1.9.3-rc1/site/clirr-report.html
> 
> RAT Report:
> http://home.apache.org/~ggregory/beanutils-1.9.3-rc1/site/rat-report.html
> 
> KEYS:
> https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> 
> This vote will close no sooner than 72 hours from now, i.e. sometime after
> 18:00 PST 5 June 2016
> 
> 
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
> 
> Thanks!
> Gary Gregory
> 
> 

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

Re: [ALL] About binary compatibility

[Oliver Heger]

Hi Benedikt,

Am 02.06.2016 um 22:42 schrieb Benedikt Ritter:
> Hi,
> 
> we do seem to have different opinions when it comes to binary compatibility
> and how it should be handled. Usually we would say "this should be decided
> on a component basis". However this discussion is coming up again and again
> and I think we should try the impossible and agree on something that we can
> document.
> 
> So here is my view on the topic:
> 
> - since our components are depended upon by a lot of projects, we need to
> take special care regarding compatibility.
> - we must not break BC in a release that could collide with an earlier
> version. In other words, when we break BC, we have to change package and
> maven coordinates.
> - BUT since we're all doing this on our spare time, there is no need to
> hold on old APIs just for the sake of it. For this reason, BC may be broken
> any time, if the steps above a followed and it has been discussed on the
> ML. Fixes can always be backported to old releases, by people who need it.
> - If there are committers who are willing to work on old version and
> committers who want to work on API redesigns, we can branch and work in
> paralell.
> - Changing the Java Language requirement does not break BC and can
> therefore be done without pumping the major version.
> 
> What is your view on the topic?

these points are rather technical ones, and most of us will probably
agree. The more important question is IMHO: when do we explicitly break
BC because we want to make use of new language features or switch to a
different design? In this area we used to be very conservative.

Take BCEL as an example. There was a strong momentum about half a year
or so ago to push out a new major release breaking BC. Then discussion
started to revert breaking changes. This would of course have been the
ideal solution for all users: getting a new version without migration
effort. However, the result was that work on reverting changes started,
but was never finished. The momentum vanished, and the release is still
overdue. So would it has been better to break BC in this case? I tend to
say yes.

Or let's discuss another component: [lang]. The last major release
happened about 5 years ago. In software business these are ages. So
would it make sense to start working on a new version focusing on Java 8
and better support for Lambdas? We could at least start something in an
experimental branch or the sandbox to experiment with new functionality.
But it is obviously not our style to do this.

It is certainly difficult to find the right balance between stability
and innovation. For our fundamental components it is for sure no good
idea to push out an incompatible major release every few months. But
every 3 or 4 years when there are significant changes in the Java
ecosystem would probably be okay.

My $0.02
Oliver

> 
> Benedikt
> 

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

Re: [LANG] Would CircuitBreaker better fit into [NET]?

[Oliver Heger]

The current implementations that we have a pretty generic and just track 
memory consumption or count events (e.g. failed service invocations). 
They are not tighed to any specific use case or domain.


I think, [lang] is a good fit, but maybe the classes can be moved to a 
separate package?


Oliver

Am 12.06.2016 um 14:37 schrieb Pascal Schumacher:

I have only see it used to prevent cascading failures in distributed
systems (see http://martinfowler.com/bliki/CircuitBreaker.html for a
detailed explanation).

Hystrix and Apache Camel contain implementations of this pattern.

Am 12.06.2016 um 14:17 schrieb James Carman:

Can it be used in non-I/O situations?

On Sun, Jun 12, 2016 at 8:15 AM sebb  wrote:


IO is a better fit than NET, but I'm not sure that it is better than
LANG.

On 12 June 2016 at 13:03, James Carman 
wrote:

It has general stream/reader stuff too.

On Sun, Jun 12, 2016 at 7:53 AM Benedikt Ritter 

wrote:

Pascal Schumacher  schrieb am So., 12. Juni

2016

um 13:50 Uhr:


Yes, so I guess Commons IO would be the best fit.


Really? When talking about I/O I always think about file system
operations...



Am 12.06.2016 um 13:40 schrieb James Carman:

Is it only I/O related?

On Sun, Jun 12, 2016 at 7:05 AM Benedikt Ritter 

Re: svn commit: r1748347 - in /commons/proper/csv/trunk/src: changes/changes.xml main/java/org/apache/commons/csv/CSVFormat.java test/java/org/apache/commons/csv/CSVPrinterTest.java

[Oliver Heger]

Just as an info, [configuration] has a similar problem. There is a
FileHandler class (in the io subpackage) which allows defining a target
file in various ways and does the conversion to streams.

Oliver

Am 14.06.2016 um 18:33 schrieb Benedikt Ritter:
> How about something like:
> 
> on CSVFormat:
> public PrintingOps print()
> 
> And the PrintingOps class would implement all the different printing
> methods, combining the CSVFormat and a printer. The call would look like:
> 
> CSVFormat.EXCEL.print().contentsOf(file, StandardCharsets.UTF_8)
> 
> sebb  schrieb am Di., 14. Juni 2016 um 17:48 Uhr:
> 
>> On 14 June 2016 at 16:27, Gary Gregory  wrote:
>>> On Jun 14, 2016 5:19 AM, "James Carman" 
>> wrote:

 Are Readers that hard to create?
>>>
>>> No, but remembering how to do this is a pain:
>>>
>>>  File out = ...
>>>
>>>  Charset charset = ...
>>>
>>>  CSVPrinter printer = new CSVPrinter(new OutputStreamWriter(new
>>> FileOutputStream(out), charset), format);
>>> Instead of:
>>>
>>> format.print(file, charset);
>>>
>>> We can roll these two APIs back out and document that the components only
>>> provides low-level APIs, forget convenience APIs.
>>>
>>> We can also find a better home for these APIs... like where? On the
>> printer
>>> static side?
>>
>> Commons IO
>>
>>> Gary
>>>
>>> Itv

 On Tue, Jun 14, 2016 at 2:17 AM Gary Gregory 
>>> wrote:

> On Mon, Jun 13, 2016 at 11:13 PM, Benedikt Ritter >>
> wrote:
>
>> I don't like how we're evolving CSVFormat. It is becoming a dumping
> ground
>> for anything that may be useful or convenient. The more methods we
>>> add,
> the
>> harder it becomes for users to find the right method for their use
>>> case.
>>
>
> Small is nice, I get that. But how would you do it differently so
>> that I
> can easily use Paths, Files, URI, and URLs...
>
> Gary
>
>
>>
>> Benedikt
>>
>>  schrieb am Di., 14. Juni 2016 um 07:53 Uhr:
>>
>>> Author: ggregory
>>> Date: Tue Jun 14 05:53:32 2016
>>> New Revision: 1748347
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1748347=rev
>>> Log:
>>> Add convenience API CSVFormat.print(File, Charset) (JIRA is down
>>> ATM).
>>>
>>> Modified:
>>> commons/proper/csv/trunk/src/changes/changes.xml
>>>
>>>
>>
>
>>>
>> commons/proper/csv/trunk/src/main/java/org/apache/commons/csv/CSVFormat.java
>>>
>>>
>>
>
>>>
>> commons/proper/csv/trunk/src/test/java/org/apache/commons/csv/CSVPrinterTest.java
>>>
>>> Modified: commons/proper/csv/trunk/src/changes/changes.xml
>>> URL:
>>>
>>
>
>>>
>> http://svn.apache.org/viewvc/commons/proper/csv/trunk/src/changes/changes.xml?rev=1748347=1748346=1748347=diff
>>>
>>>
>>
>
>>>
>> ==
>>> --- commons/proper/csv/trunk/src/changes/changes.xml (original)
>>> +++ commons/proper/csv/trunk/src/changes/changes.xml Tue Jun 14
> 05:53:32
>>> 2016
>>> @@ -40,6 +40,7 @@
>>>
>>>  
>>> due-to="Gary
>>> Gregory">Update platform requirement from Java 6 to 7.
>>> +  >> due-to="Gary
>>> Gregory">Add convenience API CSVFormat.print(File,
>> Charset)
>>>  
>>>  
>>> due-to="Gary
>>> Gregory">Make CSVPrinter.print(Object) GC-free.
>>>
>>> Modified:
>>>
>>
>
>>>
>> commons/proper/csv/trunk/src/main/java/org/apache/commons/csv/CSVFormat.java
>>> URL:
>>>
>>
>
>>>
>> http://svn.apache.org/viewvc/commons/proper/csv/trunk/src/main/java/org/apache/commons/csv/CSVFormat.java?rev=1748347=1748346=1748347=diff
>>>
>>>
>>
>
>>>
>> ==
>>> ---
>>>
>>
>
>>>
>> commons/proper/csv/trunk/src/main/java/org/apache/commons/csv/CSVFormat.java
>>> (original)
>>> +++
>>>
>>
>
>>>
>> commons/proper/csv/trunk/src/main/java/org/apache/commons/csv/CSVFormat.java
>>> Tue Jun 14 05:53:32 2016
>>> @@ -28,10 +28,14 @@ import static org.apache.commons.csv.Con
>>>  import static org.apache.commons.csv.Constants.SP;
>>>  import static org.apache.commons.csv.Constants.TAB;
>>>
>>> +import java.io.File;
>>> +import java.io.FileOutputStream;
>>>  import java.io.IOException;
>>> +import java.io.OutputStreamWriter;
>>>  import java.io.Reader;
>>>  import java.io.Serializable;
>>>  import java.io.StringWriter;
>>> +import java.nio.charset.Charset;
>>>  import java.sql.ResultSet;
>>>  import java.sql.ResultSetMetaData;
>>>  import java.sql.SQLException;
>>> @@ -864,6 +868,27 @@ public final class CSVFormat 

Re: Jenkins build is back to normal : Commons-configuration #5

[Oliver Heger]

Many thanks, Gary.

I had a look at the job configuration, but cannot see something obvious.
I guess I have to contact INFRA as sebb has proposed.

Thanks to all for the help.
Oliver

Am 28.05.2016 um 00:36 schrieb Gary Gregory:
> Done! (modify_appgroups.pl hudson-jobadmin --add=oheger)
> 
> Gary
> 
> On Fri, May 27, 2016 at 2:35 PM, Benedikt Ritter <brit...@apache.org> wrote:
> 
>> You have done that for me just two weeks ago! :o) See [1]
>>
>> Benedikt
>>
>> [1] https://wiki.apache.org/general/Jenkins#How_do_I_get_an_account
>>
>> Gary Gregory <garydgreg...@gmail.com> schrieb am Fr., 27. Mai 2016 um
>> 23:04:
>>
>>> Hm , where is that in the Jenkins UI? I do not see anything obvious? Or
>> is
>>> this done through LDAP?
>>>
>>> Gary
>>> On May 27, 2016 1:29 PM, "Benedikt Ritter" <brit...@apache.org> wrote:
>>>
>>>> Gary has the karma to make you a Jenkins Job Admin. Just ping him.
>>>>
>>>> Benedikt
>>>>
>>>> Oliver Heger <oliver.he...@oliver-heger.de> schrieb am Fr., 27. Mai
>> 2016
>>>> um
>>>> 20:54:
>>>>
>>>>> It seems that an email address of mine is hard-coded in the job
>>>>> configuration. But I do not seem to have the rights to view or even
>>>>> change the configuration :-(
>>>>>
>>>>> Oliver
>>>>>
>>>>> Am 27.05.2016 um 09:01 schrieb Apache Jenkins Server:
>>>>>> See <https://builds.apache.org/job/Commons-configuration/5/>
>>>>>>
>>>>>>
>>>>>>
>> -
>>>>>> 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 additional commands, e-mail: dev-h...@commons.apache.org

Re: Jenkins build is back to normal : Commons-configuration #5

[Oliver Heger]

It seems that an email address of mine is hard-coded in the job
configuration. But I do not seem to have the rights to view or even
change the configuration :-(

Oliver

Am 27.05.2016 um 09:01 schrieb Apache Jenkins Server:
> See 
> 
> 
> -
> 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: Jenkins build is back to normal : Commons-configuration #5

[Oliver Heger]

Am 27.05.2016 um 21:07 schrieb sebb:
> On 27 May 2016 at 19:54, Oliver Heger <oliver.he...@oliver-heger.de> wrote:
>> It seems that an email address of mine is hard-coded in the job
>> configuration.
> 
> No, but the config is set up with:
> 
> * Send separate e-mails to individuals who broke the build

Hm, at least builds #4 and #5 have been started manually. I also do not
understand, from where Jenkins drags this special email address. It is
my company address which I - to my knowledge - never used for my OSS
activities. This is what I find a bit spooky.

Oliver

> 
>> But I do not seem to have the rights to view or even
>> change the configuration :-(
>>
>> Oliver
>>
>> Am 27.05.2016 um 09:01 schrieb Apache Jenkins Server:
>>> See <https://builds.apache.org/job/Commons-configuration/5/>
>>>
>>>
>>> -
>>> 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 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: Jenkins build is back to normal : Commons-configuration #5

[Oliver Heger]

Am 27.05.2016 um 22:04 schrieb sebb:
> It looks like it may get the e-mail from your Jenkins settings:
> 
> https://builds.apache.org/user/oheger/
> 
> I cannot see that; you will have to login using your LDAP id and
> password and check the settings.
> 

Thanks for looking into this.

I did check my settings, and here my @apache mail is set. This one is
forwarded to my private mail address and not related to the company address.

Oliver

> 
> On 27 May 2016 at 20:13, Oliver Heger <oliver.he...@oliver-heger.de> wrote:
>>
>>
>> Am 27.05.2016 um 21:07 schrieb sebb:
>>> On 27 May 2016 at 19:54, Oliver Heger <oliver.he...@oliver-heger.de> wrote:
>>>> It seems that an email address of mine is hard-coded in the job
>>>> configuration.
>>>
>>> No, but the config is set up with:
>>>
>>> * Send separate e-mails to individuals who broke the build
>>
>> Hm, at least builds #4 and #5 have been started manually. I also do not
>> understand, from where Jenkins drags this special email address. It is
>> my company address which I - to my knowledge - never used for my OSS
>> activities. This is what I find a bit spooky.
>>
>> Oliver
>>
>>>
>>>> But I do not seem to have the rights to view or even
>>>> change the configuration :-(
>>>>
>>>> Oliver
>>>>
>>>> Am 27.05.2016 um 09:01 schrieb Apache Jenkins Server:
>>>>> See <https://builds.apache.org/job/Commons-configuration/5/>
>>>>>
>>>>>
>>>>> -
>>>>> 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 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 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 FileUpload 1.3.2 based on RC1

[Oliver Heger]

For the record, I voted +1, too.

Oliver

Am 26.05.2016 um 21:35 schrieb Benedikt Ritter:
> This vote passes with the following votes:
> 
> - Gary Gregory: +1
> - Jochen Wiedmann: +1
> - Benedikt Ritter: +1
> - Stian Soiland-Reyes: +1
> - Bernd Eckenfels: +1
> 
> I'll continue with the release procedure.
> 
> Thank you for reviewing!
> Benedikt
> 
> Benedikt Ritter  schrieb am Mo., 23. Mai 2016 um
> 17:23 Uhr:
> 
>> It has been a long time since the last release of Apache Commons
>> FileUpload, so I'd like to release Apache Commons FileUpload 1.3.2 based on
>> RC1.
>>
>> Apache Commons FileUpload 1.3.2 RC1 is available for review here:
>>   https://dist.apache.org/repos/dist/dev/commons/fileupload (rev 13750)
>>
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1173/commons-fileupload/commons-fileupload/1.3.2/
>>
>> These are the Maven artifacts and their hashes
>>
>> commons-fileupload-1.3.2-javadoc.jar
>> (SHA1: 12bbb300a1b61e038defb1dee85e8302d6f1bbaa)
>> commons-fileupload-1.3.2-sources.jar
>> (SHA1: 23996750d5a80dc74dad55633c2a0f3db91462cb)
>> commons-fileupload-1.3.2-test-sources.jar
>> (SHA1: 2df285ad143910759a3763fcec0cd58e8525d881)
>> commons-fileupload-1.3.2-tests.jar
>> (SHA1: 310e3713308073a0392be30c129b55e872fe48f6)
>> commons-fileupload-1.3.2,jar
>> (SHA1: 5d7491ed6ebd02b6a8d2305f8e6b7fe5dbd95f72)
>> commons-fileupload-1.3.2.pom
>> (SHA1: a4c3e5d590c2e83bba42768c5b5fbef43219b5c4)
>>
>> Details of the change since 1.3.1 are in the release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/fileupload/RELEASE-NOTES.txt
>>
>> http://home.apache.org/~britter/commons/fileupload-1.3.2-rc1/changes-report.html
>>
>> I have tested this with:
>>   JDK 1.6 and Maven 3.2.5
>>   JDK 1.7 and Maven 3.3.9
>>   JDK 1.8 and Maven 3.3.9
>> Note that commons-fileupload should be JDK 1.5 compatible, but I don't
>> have a JDK 1.5 installation on my MacBook. If someone could check the build
>> with JDK 1.5, that would be great!
>>
>> The tag is here:
>>
>> https://svn.apache.org/repos/asf/commons/proper/fileupload/tags/FILEUPLOAD_1_3_2_RC1
>>  (rev 1745203)
>>
>> Site:
>>   http://home.apache.org/~britter/commons/fileupload-1.3.2-rc1/
>> (note some *relative* links are broken and the 1.3.2 directories are not
>> yet created - these will be OK once the site is deployed)
>>
>> Clirr Report (compared to 1.3):
>>
>> http://home.apache.org/~britter/commons/fileupload-1.3.2-rc1/clirr-report.html
>> (note that the API additions have been introduced in 1.3.1 not in 1.3.2)
>>
>> RAT Report:
>>
>> http://home.apache.org/~britter/commons/fileupload-1.3.2-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 than 72 hours from now,
>> i.e. sometime after 17:30 CEST 26-May 2016
>>
>> [ ] +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

Re: [beanutils] release 1.9.3?

[Oliver Heger]

Am 31.05.2016 um 23:31 schrieb Gary Gregory:
> While there is not much new for 1.9.3, just two fixes, I would not mind
> pushing out a release, just to get the refreshed dependency on Commons
> Collection out since there has been noise about it related to security.
> 
> Thoughts?

+1, would it be possible to fix BEANUTILS-477? This came up already
multiple times. It is probably only suppressing some log output.

I am currently pretty busy, otherwise I would look into it myself.

Thanks
Oliver

> 
> Gary
> 

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

Re: Resign from PMC...

[Oliver Heger]

James,

Am 19.06.2016 um 01:36 schrieb James Carman:
> I wish to resign from the Apache Commons PMC. Thank you.
> 

sorry to hear this. Would you mind telling us something about your
reasons? - Of course, you don't have to if you don't want.

Regards
Oliver

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

Re: [VOTE] Release Apache Commons BCEL 6.0 based on RC5

[Oliver Heger]

Am 19.06.2016 um 17:56 schrieb Benedikt Ritter:
> Hello Oliver,
> 
> Oliver Heger <oliver.he...@oliver-heger.de> schrieb am So., 19. Juni 2016
> um 17:43 Uhr:
> 
>> Build works fine with Java 1.7 on Windows 10. Artifacts and site look
>> good (there are a number of PMD and findbugs warnings, but I think this
>> is acceptable).
>>
>> However, I was not able to build the site locally because of:
>>
>> [ERROR] Could not find resource
>>
>> 'c:\data\dev\projects\OpenSource\bcel\bcel-6.0-src/findbugs-exclude-filter.xml'.
>> -> [Help 1]
>>
>> This file is missing from the source distribution. This prevents me from
>> voting +1.
>>
>> Note: I did a rather technical check of the artifacts and cannot judge
>> if the content is really what the users desire.
>>
> 
> To make it easier for me to tally up votes in the end, does this mean your
> vote is -1?

I have an interest to see the release coming out, so it is a -0.

Oliver

> 
> Benedikt
> 
> 
>> Thanks
>> Oliver
>>
>> Am 18.06.2016 um 16:54 schrieb Benedikt Ritter:
>>> Hi,
>>>
>>> more then 10 years have passed since we've released BCEL 5.2. Users are
>>> waiting for us to release a new version capable of handling Java 6, 7
>> and 8
>>> byte code. There have already been 4 release candidates for BCEL 6.0 but
>>> they have not made it for various reasons. Most importantly BC has been
>>> broken. Package and Maven coordinates have been changed according to our
>>> release guidelines. However our users have asked us to provide a binary
>>> compatible release and here we are...
>>>
>>> I'd like to call a vote for releasing Apache Commons BCEL 6.0 based on
>> RC5.
>>>
>>> BCEL 6.0 RC1 is available for review here:
>>>   https://dist.apache.org/repos/dist/dev/commons/bcel (rev 14039)
>>>
>>> The tag is here:
>>>   https://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0_RC5
>> (rev
>>> 1749058)
>>>
>>> Maven artifacts are here:
>>>
>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1177/org/apache/bcel/bcel/6.0/
>>>
>>> These are the Maven artifacts and their hashes:
>>>
>>> bcel-6.0-javadoc.jar
>>> (SHA1: 79b5fd315f5f949580268e55c0baa85e18df4740)
>>> bcel-6.0-sources.jar
>>> (SHA1: f4ab6e682465471084e601c49e03a1385c610343)
>>> bcel-6.0-test-sources.jar
>>> (SHA1: 9aabf73fd9680336000f54a29fc234eaf474fc85)
>>> bcel-6.0-tests.jar
>>> (SHA1: f34db9121dd7b2dd198754416d29258a96549789)
>>> bcel-6.0.jar
>>> (SHA1: e6546a05530e8ed64b07cb917a8dca7912a16404)
>>> bcel-6.0.pom
>>> (SHA1: 76c9509859b13c74ff082e489b247708c48e59cb)
>>>
>>> I have tested this with Java 7 and 8 using Maven 3.3.9 on Mac OS 10.11.5.
>>>
>>> Details of changes since 5.2 are in the release notes:
>>>   https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-NOTES.txt
>>>
>> http://home.apache.org/~britter/commons/bcel/6.0-RC5/changes-report.html
>>>
>>> Site:
>>>   http://home.apache.org/~britter/commons/bcel/6.0-RC5/
>>> (note some *relative* links are broken and the 6.0 directories are not
>> yet
>>> created - these will be OK once the site is deployed)
>>>
>>> Clirr Report (compared to 5.2):
>>>   http://home.apache.org/~britter/commons/bcel/6.0-RC5/clirr-report.html
>>>
>>> Note that Clirr reports several errors. These have been discussed on the
>> ML
>>> already and I uploaded the site a while ago giving everybody the
>>> opportunity to raise objections against these changes. These changes are
>>> also explicitly noted in the Release notes.
>>>
>>> Furthermore java.io.Serializable has been dropped from all BCEL classes.
>> An
>>> extended Clirr report including this change can be reviewed here:
>>>
>>>
>> http://home.apache.org/~britter/commons/bcel/6.0-RC5/bcel5-bcel6-clirr-report.html
>>>
>>> We don't consider this to be a problem because we don't see a reason for
>>> users to serialize BCEL classes.
>>>
>>> RAT Report:
>>> http://home.apache.org/~britter/commons/bcel/6.0-RC5/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 17:00 CEST 21-June 2016
>>>
>>> [ ] +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 BCEL 6.0 based on RC5

[Oliver Heger]

Build works fine with Java 1.7 on Windows 10. Artifacts and site look
good (there are a number of PMD and findbugs warnings, but I think this
is acceptable).

However, I was not able to build the site locally because of:

[ERROR] Could not find resource
'c:\data\dev\projects\OpenSource\bcel\bcel-6.0-src/findbugs-exclude-filter.xml'.
-> [Help 1]

This file is missing from the source distribution. This prevents me from
voting +1.

Note: I did a rather technical check of the artifacts and cannot judge
if the content is really what the users desire.

Thanks
Oliver

Am 18.06.2016 um 16:54 schrieb Benedikt Ritter:
> Hi,
> 
> more then 10 years have passed since we've released BCEL 5.2. Users are
> waiting for us to release a new version capable of handling Java 6, 7 and 8
> byte code. There have already been 4 release candidates for BCEL 6.0 but
> they have not made it for various reasons. Most importantly BC has been
> broken. Package and Maven coordinates have been changed according to our
> release guidelines. However our users have asked us to provide a binary
> compatible release and here we are...
> 
> I'd like to call a vote for releasing Apache Commons BCEL 6.0 based on RC5.
> 
> BCEL 6.0 RC1 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/bcel (rev 14039)
> 
> The tag is here:
>   https://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0_RC5 (rev
> 1749058)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1177/org/apache/bcel/bcel/6.0/
> 
> These are the Maven artifacts and their hashes:
> 
> bcel-6.0-javadoc.jar
> (SHA1: 79b5fd315f5f949580268e55c0baa85e18df4740)
> bcel-6.0-sources.jar
> (SHA1: f4ab6e682465471084e601c49e03a1385c610343)
> bcel-6.0-test-sources.jar
> (SHA1: 9aabf73fd9680336000f54a29fc234eaf474fc85)
> bcel-6.0-tests.jar
> (SHA1: f34db9121dd7b2dd198754416d29258a96549789)
> bcel-6.0.jar
> (SHA1: e6546a05530e8ed64b07cb917a8dca7912a16404)
> bcel-6.0.pom
> (SHA1: 76c9509859b13c74ff082e489b247708c48e59cb)
> 
> I have tested this with Java 7 and 8 using Maven 3.3.9 on Mac OS 10.11.5.
> 
> Details of changes since 5.2 are in the release notes:
>   https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/bcel/6.0-RC5/changes-report.html
> 
> Site:
>   http://home.apache.org/~britter/commons/bcel/6.0-RC5/
> (note some *relative* links are broken and the 6.0 directories are not yet
> created - these will be OK once the site is deployed)
> 
> Clirr Report (compared to 5.2):
>   http://home.apache.org/~britter/commons/bcel/6.0-RC5/clirr-report.html
> 
> Note that Clirr reports several errors. These have been discussed on the ML
> already and I uploaded the site a while ago giving everybody the
> opportunity to raise objections against these changes. These changes are
> also explicitly noted in the Release notes.
> 
> Furthermore java.io.Serializable has been dropped from all BCEL classes. An
> extended Clirr report including this change can be reviewed here:
> 
> http://home.apache.org/~britter/commons/bcel/6.0-RC5/bcel5-bcel6-clirr-report.html
> 
> We don't consider this to be a problem because we don't see a reason for
> users to serialize BCEL classes.
> 
> RAT Report:
> http://home.apache.org/~britter/commons/bcel/6.0-RC5/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 17:00 CEST 21-June 2016
> 
> [ ] +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

Re: [VOTE] Release Compress 1.12 based on RC2

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. Artifacts and site
look good.

+1

Oliver

Am 18.06.2016 um 18:12 schrieb Stefan Bodewig:
> Hi all
> 
> as promised I've cut a RC for Compress 1.12.
> 
> The Release Candidate is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/compress/
>   (svn revision 14040)
> 
> Maven artifacts are here:
>   
> https://repository.apache.org/content/repositories/orgapachecommons-1178/org/apache/commons/commons-compress/1.12/
> 
> These are the Maven artifacts and their hashes
> 
> d4ba952b054eef846e7255cc3ac6d4ca76ead72c  commons-compress-1.12.pom
> 84caa68576e345eb5e7ae61a0e5a9229eb100d7b  commons-compress-1.12.jar
> 3f11c15206fe1658cb09793f551d4777edc3ac99  commons-compress-1.12-javadoc.jar
> 1fdd1a2fed15cdf08780ed564279c0ddbff46419  commons-compress-1.12-sources.jar
> 2e03ca468fbfb7c5b09bd8b626261f4dffc4ffcc  commons-compress-1.12-tests.jar
> 2b970a766b502f15170e75b9bc7cc7d880e53e2d  
> commons-compress-1.12-test-sources.jar
> 
> Details of changes since 1.11 are in the release notes:
>   https://dist.apache.org/repos/dist/dev/commons/compress/RELEASE-NOTES.txt
>   http://stefan.samaflost.de/staging/COMPRESS-1.12/changes-report.html
> 
> The tag is here:
>   
> https://git-wip-us.apache.org/repos/asf?p=commons-compress.git;a=commit;h=3623ee7dad07c74722baeeffcec6770015f915cf
> 
> Site:
>   http://stefan.samaflost.de/staging/COMPRESS-1.12
> 
>   as usual when I cut releases this is *not* the site that I'm going to
>   publish after the relase. I'll update changes.xml when I know the
>   release date. Also the javadocs for 1.12 are missing for now (they are
>   identical to the "GIT latest" ones) and the download page doesn't work
>   on my server.
> 
> Clirr Report (compared to 1.11):
>   http://stefan.samaflost.de/staging/COMPRESS-1.12/clirr-report.html
> 
> RAT Report:
>   http://stefan.samaflost.de/staging/COMPRESS-1.12/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 16:00 UTC 21-June 2016
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> 
> Stefan
> 
> -
> 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] Form a separate TLP based on [math]

[Oliver Heger]

+1

I assume this step is beneficial for [math]. Here in commons we may miss
you.

Oliver

Am 16.01.2016 um 16:18 schrieb Phil Steitz:
> The discussion has thus far been generally favorable.  I would like
> therefore to put the proposal to split [math] out into a separate
> TLP to a VOTE.  Assuming a favorable vote, we can discuss how to go
> about doing it.  Votes, please.  All are welcome to vote.
> 
> [ ] +1 I am in favor of this action
> [ ] +0 I am OK with this
> [ ] -0 OK, but...
> [ ] -1 I oppose this action because...
> 
> This VOTE will run a little longer than usual - closing at 20 Jan
> 13:00 UTC.
> 
> Thanks!
> 
> Phil
> 
> 
> -
> 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: [Math] How fast is fast enough?

[Oliver Heger]

Am 06.02.2016 um 12:31 schrieb James Carman:
> Okay, folks, this is definitely getting out of hand. Let's put a moratorium
> on this thread for the weekend or something and try to come back together
> next week and try to move forward. I would urge folks to watch this while
> we wait:
> 
> https://m.youtube.com/watch?v=rOWmrlft2FI
> 
> p.s. Phil, I do hope you'll reconsider.

Big +1! Please take some time to rethink. This would be a huge loss for
this community.

Oliver

> 
> On Fri, Feb 5, 2016 at 10:47 PM Phil Steitz  wrote:
> 
>> OK, I give up.  I am withdrawing as volunteer chair or member of the
>> new TLP.
>>
>> Phil
>>
>> On 2/5/16 7:23 PM, Gilles wrote:
>>> Phil,
>>>
>>> You talk again about me trying to push forward changes that
>>> serve no purpose besides "trash performance and correctness".
>>> This is again baseless FUD to which I've already answered
>>> (with detailed list of facts which you chose to ignore).
>>> You declare anything for which you don't have an answer as
>>> "bogus argument". Why is the reference to multi-threaded
>>> implementations bogus?  You contradict yourself in pretending
>>> that CM RNGs could be so good as to make people want to use
>>> them while refusing to consider whether another design might
>>> be better suited to such high(er)-performance extensions.
>>> This particular case is a long shot but if any and all
>>> discussions are stopped dead, how do you imagine that we can
>>> go anywhere?
>>> As you could read from experts, micro-benchmarks are deceiving;
>>> but you refuse to even consider alternative designs if there
>>> might be a slight suspicion of degradation.
>>> How can we ever set up a constructive discussion on how to
>>> make everybody enjoy this project if the purported chair is
>>> so bent to protecting existing code rather than nurture a good
>>> relationship with developers who may sometimes have other ideas?
>>> I'm trying to improve the code (in a dimension which you can't
>>> seem to understand unfortunately) but respectfully request
>>> data points from those users of said code, in order to be
>>> able to prove that no harm will be done.
>>> But you seem to prefer to not disclose anything that would
>>> get us closer to agreement (better design with similar
>>> performance and room for improvement, to be discussed
>>> together as a real development team -- Not you requiring,
>>> as a bad boss, that I bow to your standards for judging
>>> usefulness).
>>> This 1% which you throw at me, where does it come from?
>>> What does 1% mean when the benchmark shows standard deviations
>>> that vary from 4 to 26% in the "nextInt" case and from 3 to
>>> 7% in the "nextGaussian" case?
>>> This 1% looks meaningless without context; context is what I'm
>>> asking in order to try and establish objectively whether
>>> another design will have a measurable impact on actual tasks.
>>> I'm not going to show any "damaged" benchmark because of how
>>> unwelcome you make me feel every time I wish to talk about
>>> other aspects of the code.
>>> There is no development community here.  Only solitary
>>> coders who share a repository.
>>>
>>> Not sorry for the top-post,
>>> Gilles
>>>
>>>
>>> On Fri, 5 Feb 2016 17:07:16 -0700, Phil Steitz wrote:
 On 2/5/16 12:59 PM, Gilles wrote:
> On Fri, 5 Feb 2016 06:50:10 -0700, Phil Steitz wrote:
>> On 2/4/16 3:59 PM, Gilles wrote:
>>> Hi.
>>>
>>> Here is a micro-benchmark report (performed with
>>> "PerfTestUtils"):
>>> -
>>> nextInt() (calls per timed block: 200, timed blocks: 100,
>>> time
>>> unit: ms)
>>> name time/call std dev total time ratio
>>> cv difference
>>> o.a.c.m.r.JDKRandomGenerator 1.088e-05 2.8e-06 2.1761e+03 1.000
>>> 0.26 0.e+00
>>>o.a.c.m.r.MersenneTwister 1.024e-05 1.5e-06 2.0471e+03 0.941
>>> 0.15 -1.2900e+02
>>>   o.a.c.m.r.Well512a 1.193e-05 4.4e-07 2.3864e+03 1.097
>>> 0.04 2.1032e+02
>>>  o.a.c.m.r.Well1024a 1.348e-05 1.9e-06 2.6955e+03 1.239
>>> 0.14 5.1945e+02
>>> o.a.c.m.r.Well19937a 1.495e-05 2.1e-06 2.9906e+03 1.374
>>> 0.14 8.1451e+02
>>> o.a.c.m.r.Well19937c 1.577e-05 8.8e-07 3.1542e+03 1.450
>>> 0.06 9.7816e+02
>>> o.a.c.m.r.Well44497a 1.918e-05 1.4e-06 3.8363e+03 1.763
>>> 0.08 1.6602e+03
>>> o.a.c.m.r.Well44497b 1.953e-05 2.8e-06 3.9062e+03 1.795
>>> 0.14 1.7301e+03
>>>o.a.c.m.r.ISAACRandom 1.169e-05 1.9e-06 2.3375e+03 1.074
>>> 0.16 1.6139e+02
>>> -
>>> where "cv" is the ratio of the 3rd to the 2nd column.
>>>
>>> Questions are:
>>> * How meaningful are micro-benchmarks when the timed operation
>>> has
>>> a very
>>>   small duration (wrt e.g. the duration of other machine
>>> instructions that
>>>   are required to perform them)?
>>
>> It is harder to get good benchmarks for shorter duration

Re: [compress] test failures in master

[Oliver Heger]

With Java 1.6 on Windows 10 I get:

Results :

Failed tests:
  ArchiveReadTest.testArchive:103 Problem checking
c:\data\dev\projects\OpenSource\commons-compress\target\test-classes\archives\FreeBSD.ar
  ArchiveReadTest.testArchive:103 Problem checking
c:\data\dev\projects\OpenSource\commons-compress\target\test-classes\archives\SunOS.ar
  ZipArchiveInputStreamTest.testUnshrinkEntry:137 array lengths
differed, expected.length=80 actual.length=76
  ZipFileTest.testUnshrinking:258 array lengths differed,
expected.length=80 actual.length=76

Tests run: 567, Failures: 4, Errors: 0, Skipped: 2

I don't get your 6 errors. With Java 1.5 I get 19 errors, but these seem
to be all OutOfMemoryErrors.

Oliver

Am 06.04.2016 um 21:29 schrieb Gary Gregory:
> Frak! Must be a Windows issue :-( Anyone on Windows who can test this?
> 
> TY,
> GG
> 
> On Wed, Apr 6, 2016 at 10:56 AM, Matt Sicker  wrote:
> 
>> What, no Jenkins job? ;)
>>
>> mvn clean verify works fine for me on Mac OS X.
>>
>> On 6 April 2016 at 12:40, Gary Gregory  wrote:
>>
>>> I get:
>>>
>>> Failed tests:
>>>   ArchiveReadTest.testArchive:103 Problem checking
>>>
>>>
>> E:\vcs\git\apache\commons\commons-compress\target\test-classes\archives\FreeBSD.ar
>>>   ArchiveReadTest.testArchive:103 Problem checking
>>>
>>>
>> E:\vcs\git\apache\commons\commons-compress\target\test-classes\archives\SunOS.ar
>>>   ZipArchiveInputStreamTest.testUnshrinkEntry:137 array lengths differed,
>>> expected.length=80 actual.length=76
>>>   ZipFileTest.testUnshrinking:258 array lengths differed,
>>> expected.length=80 actual.length=76
>>> Tests in error:
>>>   DetectArchiverTestCase.testDetection:68->getStreamFor:101 » Archive No
>>> Archive...
>>>   LongPathTest.testArchive:116 » Archive No Archiver found for the stream
>>> signat...
>>>
>>  ArArchiveInputStreamTest.testReadLongNamesBSD:40->checkLongNameEntry:48 »
>>> IO i...
>>>
>>  ArArchiveInputStreamTest.testReadLongNamesGNU:35->checkLongNameEntry:48 »
>>> IO i...
>>>   ChangeSetTestCase.testDeleteFromAndAddToAr:1018 » IO invalid header
>>> !
>>>   ChangeSetTestCase.testDeleteFromAr:972 » IO invalid header !
>>>
>>> Tests run: 567, Failures: 4, Errors: 6, Skipped: 2
>>>
>>> When running from got master, and even with the commit for "Merge tag
>>> 'rel/1.11' and bump version"
>>>
>>> Is this a Windows only issue?
>>>
>>> Tested with:
>>>
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
>>> 05:51:28-0800)
>>> Maven home: E:\Java\apache-maven-3.0.5
>>> Java version: 1.5.0_22, vendor: Sun Microsystems Inc.
>>> Java home: E:\Program Files\Java\jdk1.5.0_22\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>>> Wed 04/06/2016 10:40:30.18
>>>
>>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>>> 2015-11-10T08:41:47-08:00)
>>> Maven home: E:\Java\apache-maven-3.3.9\bin\..
>>> Java version: 1.8.0_77, vendor: Oracle Corporation
>>> Java home: C:\Program Files\Java\jdk1.8.0_77\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
>>>
>>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>>> 2015-11-10T08:41:47-08:00)
>>> Maven home: E:\Java\apache-maven-3.3.9\bin\..
>>> Java version: 1.7.0_79, vendor: Oracle Corporation
>>> Java home: C:\Program Files\Java\jdk1.7.0_79\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>>>
>>> TY,
>>> GG
>>>
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> 
>>> JUnit in Action, Second Edition 
>>> Spring Batch in Action 
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>
>>
>>
>> --
>> Matt Sicker 
>>
> 
> 
> 

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

Re: [compress] test failures in master

[Oliver Heger]

Am 07.04.2016 um 21:18 schrieb Stefan Bodewig:
> On 2016-04-07, sebb wrote:
> 
>> On 7 April 2016 at 10:19, Stefan Bodewig  wrote:
> 
>> I set up
> 
>> https://builds.apache.org/job/Commons-Compress-Windows/
> 
> Thanks!
> 
>> Most tests failed with
> 
>> java.lang.OutOfMemoryError: Java heap space
> 
>> If someone can suggest a suitable setting I can update the build job.
> 
> Maybe pick java6 or higher? I think Oliver said he has seen the OOMs
> only for Java5 on Windows.

True, I can confirm that the OOMs are gone with a Java version > 1.5.

Oliver

> 
>>> This could be testcases that are sensitive to line-ends.
> 
>> If so,can these be fixed - or disabled - for Windows?
> 
> Ideally they can be fixed, but I haven't found the time to look into
> them - and likely won't for the next days.
> 
> Stefan
> 
> -
> 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 Configuration 2.0 based on RC1

[Oliver Heger]

Hi Benedikt,

Am 21.03.2016 um 09:58 schrieb Benedikt Ritter:
> Hello Oliver,
> 
> very nice artifacts, good work.
> 
> - builds with java 6, 7 and 8
> - site looks good
> - reports look good
> 
> Only thing I found is:
> - build.xml and build.properties.sample are in the tag but not in the src
> archive. The ant build can probably be dropped (does it work anyway?). No
> blocker for me.
> 
> +1

thanks for the review.

You are right, the ant-related files should be part of the source
distribution. build.xml should be pretty up-to-date. However,
maintaining two different build files is a pain and error-prone. The
trend seems to be dropping the ant build. I would be in favor of this.

Oliver

> 
> Benedikt
> 
> Oliver Heger <oliver.he...@oliver-heger.de> schrieb am So., 20. März 2016
> um 22:42 Uhr:
> 
>> Hi all,
>>
>> after a series of alpha and beta releases, I think we are now ready to
>> release the final 2.0 version of [configuration]. So this is the
>> corresponding release vote.
>>
>> Configuration 2.0 RC1 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/configuration
>> (revision 12797)
>>
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1143
>>
>> Details of changes since 1.10 and the previous beta version are in the
>> release notes:
>>
>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
>>
>> https://home.apache.org/~oheger/configuration-2.0-rc1/changes-report.html
>>
>> Here is the tag:
>>
>>
>> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_0_RC1
>> (revision 1735904)
>>
>> Site:
>>https://home.apache.org/~oheger/configuration-2.0-rc1/
>> (note some links in the menu are not yet working)
>>
>> KEYS:
>>   http://www.apache.org/dist/commons/KEYS
>>
>> Please review the release candidate and vote.
>> This vote will close no sooner than 72 hours from now, i.e. after 2200
>> GMT 23-Mar 2016
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>> Thanks!
>> Oliver
>>
>>
>>
>> -
>> 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 Configuration 2.0 based on RC1

[Oliver Heger]

Am 22.03.2016 um 01:32 schrieb James Carman:
> +1 drop ant

So we agree on this one. What about the actual vote? (Nudge, nudge)

Oliver

> 
> On Mon, Mar 21, 2016 at 5:06 PM Oliver Heger <oliver.he...@oliver-heger.de>
> wrote:
> 
>> Hi Benedikt,
>>
>> Am 21.03.2016 um 09:58 schrieb Benedikt Ritter:
>>> Hello Oliver,
>>>
>>> very nice artifacts, good work.
>>>
>>> - builds with java 6, 7 and 8
>>> - site looks good
>>> - reports look good
>>>
>>> Only thing I found is:
>>> - build.xml and build.properties.sample are in the tag but not in the src
>>> archive. The ant build can probably be dropped (does it work anyway?). No
>>> blocker for me.
>>>
>>> +1
>>
>> thanks for the review.
>>
>> You are right, the ant-related files should be part of the source
>> distribution. build.xml should be pretty up-to-date. However,
>> maintaining two different build files is a pain and error-prone. The
>> trend seems to be dropping the ant build. I would be in favor of this.
>>
>> Oliver
>>
>>>
>>> Benedikt
>>>
>>> Oliver Heger <oliver.he...@oliver-heger.de> schrieb am So., 20. März
>> 2016
>>> um 22:42 Uhr:
>>>
>>>> Hi all,
>>>>
>>>> after a series of alpha and beta releases, I think we are now ready to
>>>> release the final 2.0 version of [configuration]. So this is the
>>>> corresponding release vote.
>>>>
>>>> Configuration 2.0 RC1 is available for review here:
>>>> https://dist.apache.org/repos/dist/dev/commons/configuration
>>>> (revision 12797)
>>>>
>>>> Maven artifacts are here:
>>>>
>>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1143
>>>>
>>>> Details of changes since 1.10 and the previous beta version are in the
>>>> release notes:
>>>>
>>>>
>>>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
>>>>
>>>>
>> https://home.apache.org/~oheger/configuration-2.0-rc1/changes-report.html
>>>>
>>>> Here is the tag:
>>>>
>>>>
>>>>
>> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_0_RC1
>>>> (revision 1735904)
>>>>
>>>> Site:
>>>>https://home.apache.org/~oheger/configuration-2.0-rc1/
>>>> (note some links in the menu are not yet working)
>>>>
>>>> KEYS:
>>>>   http://www.apache.org/dist/commons/KEYS
>>>>
>>>> Please review the release candidate and vote.
>>>> This vote will close no sooner than 72 hours from now, i.e. after 2200
>>>> GMT 23-Mar 2016
>>>>
>>>>   [ ] +1 Release these artifacts
>>>>   [ ] +0 OK, but...
>>>>   [ ] -0 OK, but really should fix...
>>>>   [ ] -1 I oppose this release because...
>>>>
>>>> Thanks!
>>>> Oliver
>>>>
>>>>
>>>>
>>>> -
>>>> 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 additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Accept Chimera as new Apache Commons Component

[Oliver Heger]

Since we already started to use fractional numbers, I would be +0.5.

I am also worried about the JNI stuff, but I think a new group of
developers would be good for this community.

Oliver

Am 21.03.2016 um 09:45 schrieb Benedikt Ritter:
> Hi all,
> 
> after long discussions I think we have gathered enough information to
> decide whether we want to accept the Chimera project as a new Apache
> Commons component.
> 
> Proposed name: Apache Commons Crypto
> Proposal text:
> https://github.com/intel-hadoop/chimera/blob/master/PROPOSAL.html
> Initial Code Base:  https://github.com/intel-hadoop/chimera/
> Initial Committers (Names in alphabetical order):
> - Aaron T. Myers (a...@apache.org, Apache Hadoop PMC, one of the original
> Crypto dev team in Apache Hadoop)
> - Andrew Wang (w...@apache.org, Apache Hadoop PMC, one of the original
> Crypto dev team in Apache Hadoop)
> - Chris Nauroth (cnaur...@apache.org, Apache Hadoop PMC and active
> reviewer)
> - Colin P. McCabe (cmcc...@apache.org, Apache Hadoop PMC, one of the
> original Crypto dev team in Apache Hadoop)
> - Dapeng Sun (s...@apache.org, Apache Sentry Committer, Chimera contributor)
> - Dian Fu (dia...@apache.org, Apache Sqoop Committer, Chimera contributor)
> - Dong Chen (do...@apache.org, Apache Hive Committer,interested on Chimera)
> - Ferdinand Xu (x...@apache.org, Apache Hive Committer, Chimera contributor)
> - Haifeng Chen (haifengc...@apache.org, Chimera lead and code contributor)
> - Marcelo Vanzin (Apache Spark Committer, Chimera contributor)
> - Uma Maheswara Rao G (umamah...@apache.org, Apache Hadoop PMC, One of the
> original Crypto dev/review team in Apache Hadoop)
> - Yi Liu (y...@apache.org, Apache Hadoop PMC, One of the original Crypto
> dev/review team in Apache Hadoop)
> 
> Please review the proposal and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 0900
> GMT 24-Mar 2016
> 
>   [ ] +1 Accept Chimera as new Apache Commons Component
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this because...
> 
> Thank you!
> Benedikt
> 

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

Re: [VOTE] Release Configuration 2.0 based on RC1

[Oliver Heger]

Hi Emmanuel,

Am 22.03.2016 um 21:22 schrieb Emmanuel Bourg:
> Thank you very much pushing [configuration] forward Oliver. I haven't
> looked at [configuration] for a long time, my needs are rather basic and
> a mere read-only PropertiesConfiguration is good enough for me. There is
> one change though I hoped could get into 2.0, that was the integration
> of DataConfiguration into Configuration (or ImmutableConfiguration now).
> Adding more methods to the interface was impossible on the 1.x line and
> I thought we could do that for 2.0.

it is true that the lots of methods of DataConfiguration have not been
integrated into the main configuration interfaces. However, there are at
least some new generic get() methods that allow specifying a result
class and are directly connected to the data conversion facilities. This
is maybe a bit less convenient than having a rich interface with many
possible result types, but one can achieve the same results.

Oliver

> 
> Emmanuel Bourg
> 
> 
> Le 20/03/2016 22:42, Oliver Heger a écrit :
>> Hi all,
>>
>> after a series of alpha and beta releases, I think we are now ready to
>> release the final 2.0 version of [configuration]. So this is the
>> corresponding release vote.
>>
>> Configuration 2.0 RC1 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/configuration
>> (revision 12797)
>>
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1143
>>
>> Details of changes since 1.10 and the previous beta version are in the
>> release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
>>
>> https://home.apache.org/~oheger/configuration-2.0-rc1/changes-report.html
>>
>> Here is the tag:
>>
>> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_0_RC1
>> (revision 1735904)
>>
>> Site:
>>https://home.apache.org/~oheger/configuration-2.0-rc1/
>> (note some links in the menu are not yet working)
>>
>> KEYS:
>>   http://www.apache.org/dist/commons/KEYS
>>
>> Please review the release candidate and vote.
>> This vote will close no sooner than 72 hours from now, i.e. after 2200
>> GMT 23-Mar 2016
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>> Thanks!
>> Oliver
>>
>>
>>
>> -
>> 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 additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Configuration 2.0 based on RC1

[Oliver Heger]

My +1

Oliver

Am 20.03.2016 um 22:42 schrieb Oliver Heger:
> Hi all,
> 
> after a series of alpha and beta releases, I think we are now ready to
> release the final 2.0 version of [configuration]. So this is the
> corresponding release vote.
> 
> Configuration 2.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/configuration
> (revision 12797)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1143
> 
> Details of changes since 1.10 and the previous beta version are in the
> release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
> 
> https://home.apache.org/~oheger/configuration-2.0-rc1/changes-report.html
> 
> Here is the tag:
> 
> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_0_RC1
> (revision 1735904)
> 
> Site:
>https://home.apache.org/~oheger/configuration-2.0-rc1/
> (note some links in the menu are not yet working)
> 
> KEYS:
>   http://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 2200
> GMT 23-Mar 2016
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> Oliver
> 
> 
> 
> -
> 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

[ANNOUNCEMENT] Commons Configuration 2.0 Released

[Oliver Heger]

The Apache Commons Team is pleased to announce the availability of
Apache Commons Configuration 2.0.

The Commons Configuration software library provides a generic
configuration interface which enables an application to read
configuration data from a variety of sources.

After a series of alpha and beta releases, this is the first final
release for Apache Commons Configuration 2.0.

Version 2 is a major redesign of the Configuration API. It breaks
compatibility in many areas and, therefore, is not a drop-in replacement
for Commons Configuration 1.x. Changes on client code are required. If
you want to upgrade from Commons Configuration 1.x to the new version,
make sure to consult the upgrade guide at
  http://commons.apache.org/configuration/userguide/upgradeto2_0.html
which describes the breaking changes.

A full list of all changes can be found in the release notes at
  http://www.apache.org/dist/commons/configuration/RELEASE-NOTES.txt

The user's guide has been updated to describe all the new features of
Configuration 2.0. It can be found at
  http://commons.apache.org/configuration/userguide/user_guide.html


Source and binary distributions are available for download from the
Apache Commons download site:

http://commons.apache.org/proper/commons-configuration/download_configuration.cgi

Please verify signatures using the KEYS file available at the above
location when downloading the release.

For complete information on Commons Configuration, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Configuration website:

http://commons.apache.org/proper/commons-configuration/

Oliver Heger, on behalf of the Apache Commons community

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

[RESULT][VOTE] Release Configuration 2.0 based on RC1

[Oliver Heger]

The vote to release Configuration 2.0 based on RC1 has passed with the
following votes (all binding):

Benedikt:   +1
Luc:+1
Emmanuel:   +1
Oliver: +1

No other votes were cast.

Thanks to all for reviews and comments.

Oliver  

Am 20.03.2016 um 22:42 schrieb Oliver Heger:
> Hi all,
> 
> after a series of alpha and beta releases, I think we are now ready to
> release the final 2.0 version of [configuration]. So this is the
> corresponding release vote.
> 
> Configuration 2.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/configuration
> (revision 12797)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1143
> 
> Details of changes since 1.10 and the previous beta version are in the
> release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
> 
> https://home.apache.org/~oheger/configuration-2.0-rc1/changes-report.html
> 
> Here is the tag:
> 
> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_0_RC1
> (revision 1735904)
> 
> Site:
>https://home.apache.org/~oheger/configuration-2.0-rc1/
> (note some links in the menu are not yet working)
> 
> KEYS:
>   http://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 2200
> GMT 23-Mar 2016
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> Oliver
> 
> 
> 
> -
> 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

[VOTE] Release Configuration 2.0 based on RC1

[Oliver Heger]

Hi all,

after a series of alpha and beta releases, I think we are now ready to
release the final 2.0 version of [configuration]. So this is the
corresponding release vote.

Configuration 2.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/configuration
(revision 12797)

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1143

Details of changes since 1.10 and the previous beta version are in the
release notes:

https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt

https://home.apache.org/~oheger/configuration-2.0-rc1/changes-report.html

Here is the tag:

http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_0_RC1
(revision 1735904)

Site:
   https://home.apache.org/~oheger/configuration-2.0-rc1/
(note some links in the menu are not yet working)

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

Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now, i.e. after 2200
GMT 23-Mar 2016

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

Thanks!
Oliver



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

Re: [VOTE] Release Compress 1.11 Based on RC2

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. Artifacts and site
look good.

The build with Java 1.5 failed for me because of OutOfMemory errors in a
number of test cases. I vaguely remember that I had similar problems
with previous versions; so this is not blocking.

+1

Oliver

Am 02.04.2016 um 21:25 schrieb Stefan Bodewig:
> Hi all
> 
> due to a packaging glitch I had to re-roll the release. It is based on
> the same commit that was used for RC1, so both tags refer to the same
> commit. For this reason I haven't even re-created the site.
> 
> Compress 1.11 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/compress/
> (svn revision 12977)
> 
> sha1 checksums:
> 
> b26a5bfb8686a42d256562d0a71ee436f81495e5 
> binaries/commons-compress-1.11-bin.tar.gz
> 65abf5df38d665bea3c6c215d247a26f328c84c5 
> binaries/commons-compress-1.11-bin.zip
> 3dd2e40fba93ee3c271187cc204b5b367e671847 
> source/commons-compress-1.11-src.tar.gz
> 0b053fc7937655797c7d6aa0d166d697fb4b1bae source/commons-compress-1.11-src.zip
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1145/org/apache/commons/commons-compress/1.11/
> 
> Details of changes since 1.10 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/compress/RELEASE-NOTES.txt
> http://stefan.samaflost.de/staging/COMPRESS-1.11/changes-report.html
> 
> I have tested this with JDK 1.7 and 1.8 using maven3.
> 
> The tag is here:
> 
> https://git-wip-us.apache.org/repos/asf?p=commons-compress.git;a=commit;h=ff38bf57378c7cae8617b3c8df692a5ffbe7b83f
> (the tag with the name COMPRESS-1.11-RC2 on commit ff38bf5)
> 
> Site:
> http://stefan.samaflost.de/staging/COMPRESS-1.11/
> (note this is not the site I'll publish once the vote gets accepted,
> I'll recreate the site when the release date ist fixed.
> Also download page and the 1.11 javadoc are not expected to work
> right now but will with the correct site)
> 
> Clirr Report (compared to 1.10):
> http://stefan.samaflost.de/staging/COMPRESS-1.11/clirr-report.html
> 
> RAT Report:
> http://stefan.samaflost.de/staging/COMPRESS-1.11/rat-report.html
> 
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
>   This vote will close no sooner than 72 hours from now, i.e. after
>   1930 GMT 05-April 2016
> 
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
> 
> Thanks!
> 
> Stefan
> 
> -
> 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] Commons NET 3.5 based on RC3

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. Artifacts and site
look good.

+1

Oliver

Am 02.05.2016 um 01:12 schrieb sebb:
> Try again.
> 
> ==
> 
> NET 3.5 RC3 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/net/3.5_RC3/ (13489)
> 
> commons-net-3.5-bin.tar.gz.sha1:4941d802a78dd198786d4f6a0a9500f658f44a85
> commons-net-3.5-bin.zip.sha1:b03fc180862aff92de7aaa6ca94b83ef7f3435cf
> commons-net-3.5-src.tar.gz.sha1:1215a0df6fe67cc2671679f58b29dede752f232d
> commons-net-3.5-src.zip.sha1:ea576c3a5f7d83d037e0ee9dcedb98a5ac076c1a
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1158/commons-net/commons-net/3.5/
> 
> These are the artifacts and their hashes
> 
> commons-net-3.5-test-sources.jar
> (SHA1: 5172e1c4f6544eb7755f034c89b812714fead83d)
> commons-net-3.5-sources.jar
> (SHA1: 185dea3736a8583323da4d6ce647719ddf452ccf)
> commons-net-3.5-ftp.jar
> (SHA1: 6e28fe5e21df8e2b1f166f85d69820f844c0d48e)
> commons-net-3.5.jar
> (SHA1: 342fc284019f590e1308056990fdb24a08f06318)
> commons-net-3.5-examples.jar
> (SHA1: 6272d80e897347c3c5f3691c8d76eae5deb764e1)
> commons-net-3.5-tests.jar
> (SHA1: b8925a81e0e7ed09e81341f17f1408dd6fec6f43)
> commons-net-3.5.pom
> (SHA1: d0306becf8a919442cf01a925ffaadd67dead3cf)
> commons-net-3.5-javadoc.jar
> (SHA1: 72850d3da769c0ea7b7dad00da52b7912140aee0)
> 
> 
> Details of changes since 3.4 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/net/3.5_RC3/RELEASE-NOTES.txt
> http://home.apache.org/~sebb/net-3.5-RC3/changes-report.html
> 
>   I have tested this with JDK 1.6, 7, 8 using Apache Maven 3.3.9
> 
> Note: Maven 3.1.1 works too, but has problems with the Nexus deploy -
> peer not authenticated
> Maven 3.2.5 also fails to deploy - Could not generate DH keypair
> 
>   The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_5_RC3/
> (1741905)
> 
>   Site:
> http://home.apache.org/~sebb/net-3.5-RC3/
>(some *relative* links are broken - these will be OK once the site
> is deployed)
> 
>   Clirr Report (compared to 3.4):
> http://home.apache.org/~sebb/net-3.5-RC3/clirr-report.html
> 
>   RAT Report:
> http://home.apache.org/~sebb/net-3.5-RC3/rat-report.html
> 
>   KEYS:
>   https://www.apache.org/dist/commons/KEYS
> 
>   Please review the release candidate and vote.
>   This vote will close no sooner than 72 hours from now,
>   i.e. sometime after 23:30 GMT 4 May 2016
> 
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
>   Sebb
> 
> -
> 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 commons-io 2.5 based on RC4

[Oliver Heger]

Hi Benson,

when checking the RC I get a pretty strange effect on downloading the
binaries from https://dist.apache.org/repos/dist/dev/commons/io/binaries/:

The browser shows me "dist - Revision 13260: /dev/commons/io/binaries".
However, the downloaded artifacts are obviously the ones from the
previous RC created by Kristian. So either my browser has a caching
issue or the binary artifacts have not correctly been uploaded to svn.
The source distributions are correct.

Can anybody double-check whether the problem is on my side?

Oliver

Am 14.04.2016 um 17:41 schrieb Benson Margulies:
> Commons-io 2.5 is offered for a release vote.
> 
> Commons-io 2.5 RC4 materials are available for review here:
> https://dist.apache.org/repos/dist/dev/commons/io/ (svn revision 13247)
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1174/org/apache/commons/commons-io/2.5
>   Details of changes since 2.4 are in the release notes:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310477=12322486
> 
>   I have tested this with JDK 1.6 using maven 3.0.4.
> 
>   The tag is here:
> 
> http://svn.apache.org/repos/asf/commons/proper/foo/tags/commons-io-2.5-RC4/
> (1739100)
>   N.B. the SVN revision is required because SVN tags are not immutable.
> 
>   Site:
> http://people.apache.org/~bimargules/commons-io-2.5-RC4/
>   (note some *relative* links are broken and the 1.2 directories are
>   not yet created - these will be OK once the site is deployed)
> 
>   Clirr Report (compared to 1.1):
> http://people.apache.org/~bimargulies/commons-io-2.5-RC4/clirr-report.html
> 
>   RAT Report:
> http://people.apache.org/~bimargulies/commons-io-2.5-RC4/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. after
> 0400 GMT 31-March 2010
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
> benson
> 
> -
> 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 commons-io 2.5 based on RC4

[Oliver Heger]

Build works fine with Java 1.6 on Windows 10. Artifacts and site look good.

+1

Oliver

Am 14.04.2016 um 17:41 schrieb Benson Margulies:
> Commons-io 2.5 is offered for a release vote.
> 
> Commons-io 2.5 RC4 materials are available for review here:
> https://dist.apache.org/repos/dist/dev/commons/io/ (svn revision 13247)
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1174/org/apache/commons/commons-io/2.5
>   Details of changes since 2.4 are in the release notes:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310477=12322486
> 
>   I have tested this with JDK 1.6 using maven 3.0.4.
> 
>   The tag is here:
> 
> http://svn.apache.org/repos/asf/commons/proper/foo/tags/commons-io-2.5-RC4/
> (1739100)
>   N.B. the SVN revision is required because SVN tags are not immutable.
> 
>   Site:
> http://people.apache.org/~bimargules/commons-io-2.5-RC4/
>   (note some *relative* links are broken and the 1.2 directories are
>   not yet created - these will be OK once the site is deployed)
> 
>   Clirr Report (compared to 1.1):
> http://people.apache.org/~bimargulies/commons-io-2.5-RC4/clirr-report.html
> 
>   RAT Report:
> http://people.apache.org/~bimargulies/commons-io-2.5-RC4/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. after
> 0400 GMT 31-March 2010
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
> benson
> 
> -
> 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] Commons-net 3.5 based on RC1

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. Artifacts and site
look good.

+1

One thing I find a bit strange: In the release notes it is mentioned
that the release is not source compatible to the previous one because of
a method added to an interface. However, the clirr report only contains
a single info message; I would expect an error here.

Oliver

Am 16.04.2016 um 00:42 schrieb sebb:
> It's about time to release the next version of NET.
> 
> ==
> 
> NET 3.5 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/net/
> (revision 13271)
> 
> binaries/commons-net-3.5-bin.tar.gz.sha1:798851e256b64d6d03739bc24418369de3f9da7d
> binaries/commons-net-3.5-bin.zip.sha1:2418808e04005aa706de8e62e5592d32be1f34fc
> source/commons-net-3.5-src.tar.gz.sha1:8ccedbbf247ad916f0e2f0d57b8a68c7784db1bb
> source/commons-net-3.5-src.zip.sha1:f72bd8b5bf734930107b185588c6fe695513c270
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1149/commons-net/commons-net/3.5/
> 
> These are the artifacts and their hashes
> 
> /commons-net/commons-net/3.5/commons-net-3.5-test-sources.jar
> (SHA1: be2a7e5b07fb693ce02e0b1982d31484b9974670)
> /commons-net/commons-net/3.5/commons-net-3.5-sources.jar
> (SHA1: 1f3a44fe2766e3fb333150235c108bbf21f56163)
> /commons-net/commons-net/3.5/commons-net-3.5-ftp.jar
> (SHA1: e32bf348565421a1c55625e5830737f4019dbe52)
> /commons-net/commons-net/3.5/commons-net-3.5.jar
> (SHA1: f497c63d2be3180a54122245938230ca9e3bb5a2)
> /commons-net/commons-net/3.5/commons-net-3.5-examples.jar
> (SHA1: a719e650f46c499551752c458ef1bcf9ed4ef940)
> /commons-net/commons-net/3.5/commons-net-3.5-tests.jar
> (SHA1: ba42d4ef89e8c940f111218c77875299faef22b4)
> /commons-net/commons-net/3.5/commons-net-3.5.pom
> (SHA1: 284b24dfd9cc4f0bf23c8d2ff4d95bc70fb374dc)
> /commons-net/commons-net/3.5/commons-net-3.5-javadoc.jar
> (SHA1: d858126e2260adf6e8ed2b84e12acabb7fce17ad)
> 
>   Details of changes since 3.4 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/net/RELEASE-NOTES.txt
> http://home.apache.org/~sebb/net-3.5-RC1/changes-report.html
> 
>   I have tested this with JDK 1.6, 1.7, 1.8 using Apache Maven 3.3.3
> 
>   The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_5_RC1/
> (revision 1739355)
> 
>   Site:
> http://home.apache.org/~sebb/net-3.5-RC1/
>(some *relative* links are broken - these will be OK once the site
> is deployed)
> 
>   Clirr Report (compared to 3.4):
> http://home.apache.org/~sebb/net-3.5-RC1/clirr-report.html
> 
>   RAT Report:
> http://home.apache.org/~sebb/net-3.5-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 than 72 hours from now,
>   i.e. sometime after 23:00 GMT 18 Apr 2016
> 
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
>   Sebb
> 
> -
> 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: svn commit: r1742696 - /commons/proper/configuration/trunk/build.xml

[Oliver Heger]

Am 08.05.2016 um 10:51 schrieb Dennis Kieselhorst:
> Am 07.05.2016 um 16:44 schrieb Oliver Heger:
>> Thank you for updating build.xml.
>>
>> There has been some discussion to drop the ant build completely as it
>> tends to become outdated. Most Commons components already did this, and
>> I would be in favor of this.
>>
>>
> Definitely +1, I was wondering why the Ant build script is still in
> place, but as it was modified for every release I thought it's still
> needed. The building doc
> (http://commons.apache.org/proper/commons-configuration/building.html)
> refers to some special Ant JavaCC stuff, but this should also be
> possible with javacc-maven-plugin?!

Yes, the maven build handles JavaCC invocations correctly. The building
guide would have to be updated, too, when the ant build is dropped.

Oliver

> 
> Regards
> Dennis
> 
> -
> 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: [configuration] continuous integration

[Oliver Heger]

Hi Dennis,

Am 07.05.2016 um 11:35 schrieb Dennis Kieselhorst:
> Hi!
> 
> http://commons.apache.org/proper/commons-configuration/integration.html
> links to https://continuum-ci.apache.org which no longer exists. What
> about setting up a job on http://builds.apache.org?

no objections from my side.

Thanks
Oliver

> 
> Regards
> Dennis
> 
> -
> 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 CSV 1.3 based on RC1

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. Artifacts and site
look good.

+1

Oliver

Am 06.05.2016 um 10:12 schrieb Benedikt Ritter:
> Hi,
> 
> we have fixed some bugs and added some nice new features since we released
> Apache Commons CSV 1.2. So I'd like to release Apache Commons CSV 1.3 based
> on RC 1.
> 
> Apache Commons CSV 1.3 RC1 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/csv/csv-1.3-RC1 (revision
> 13550)
> 
> Maven artifacty are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1165/org/apache/commons/commons-csv/1.3/
> 
> These are the Maven artifacts and their hashes:
> 
> commons-csv-1.3-javadoc.jar
> (SHA1: dfeed187293d2d5ed3f8b26e096474ff8350a254)
> commons-csv-1.3-sources.jar
> (SHA1: 7841722762e93d6bd4419f91e140b6a16e167fe1)
> commons-csv-1.3-test-sources.jar
> (SHA1: c6c90708e686e1a17441632e417ccf91d78d87f2)
> commons-csv-1.3-tests.jar
> (SHA1: fdf822005dca524c329c3fd2f0abc149a885b52a)
> commons-csv-1.3.jar
> (SHA1: aeed8320e1b86b27e0b477a898eb7dd049526963)
> commons-csv-1.3.pom
> (SHA1: 8916753d403a30d53b9a105372eee620cd53b802)
> 
> Details of changes since 1.2 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/csv/csv-1.3-RC1/RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/csv-1.3-RC1/changes-report.html
> 
> I have tested this on Mac OS 10.11.4 with:
>   JDK 1.6 & Maven 3.2.5
>   JDK 7 & Maven 3.3.9
>   JDK 8 & Maven 3.3.9
> 
> The tag is here:
>   https://svn.apache.org/repos/asf/commons/proper/csv/tags/csv-1.3-RC1
>  (revision 1742508)
> 
> Site:
>http://home.apache.org/~britter/commons/csv-1.3-RC1
> (note some *relative links are broken and the 1.3 directories are not yet
> created - these will be ok once the site is deployed)
> (also note the site navigation has a minor error. There are two entires for
> JavaDoc 1.2 and Site Archive 1.2. I will correct that once the site is
> deployed)
> 
> Clirr Report (compared to 1.2):
>   http://home.apache.org/~britter/commons/csv-1.3-RC1/clirr-report.html
> 
> RAT Report:
>http://home.apache.org/~britter/commons/csv-1.3-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 10:30 CEST (UTC+2)
> 09-May 2016
> 
> [ ] +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

Re: svn commit: r1742696 - /commons/proper/configuration/trunk/build.xml

[Oliver Heger]

Thank you for updating build.xml.

There has been some discussion to drop the ant build completely as it
tends to become outdated. Most Commons components already did this, and
I would be in favor of this.

WDYT?
Oliver

Am 07.05.2016 um 11:41 schrieb d...@apache.org:
> Author: deki
> Date: Sat May  7 09:41:40 2016
> New Revision: 1742696
> 
> URL: http://svn.apache.org/viewvc?rev=1742696=rev
> Log:
> align versions to fix build
> 
> Modified:
> commons/proper/configuration/trunk/build.xml
> 
> Modified: commons/proper/configuration/trunk/build.xml
> URL: 
> http://svn.apache.org/viewvc/commons/proper/configuration/trunk/build.xml?rev=1742696=1742695=1742696=diff
> ==
> --- commons/proper/configuration/trunk/build.xml (original)
> +++ commons/proper/configuration/trunk/build.xml Sat May  7 09:41:40 2016
> @@ -52,7 +52,7 @@
>
>   
>   
> - location="${lib}/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar"/>
> + location="${lib}/commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar"/>
>   location="${lib}/org/apache/commons/commons-lang3/3.3.2/commons-lang3-3.3.2.jar"/>
>   location="${lib}/commons-logging/commons-logging/1.1.3/commons-logging-1.1.3.jar"/>
>   location="${lib}/commons-beanutils/commons-beanutils/1.9.2/commons-beanutils-1.9.2.jar"/>
> @@ -73,7 +73,7 @@
>  
>   
>   
> -  location="${lib}/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar"/>
> +  location="${lib}/commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar"/>
>   location="${lib}/org/apache/commons/commons-lang3/3.3.2/commons-lang3-3.3.2.jar"/>
>location="${lib}/commons-logging/commons-logging/1.1.3/commons-logging-1.1.3.jar"/>
>location="${lib}/commons-beanutils/commons-beanutils/1.9.2/commons-beanutils-1.9.2.jar"/>
> @@ -276,19 +276,19 @@
>depends="init" 
>description="Download all dependencies">
> -
> - src="http://repo1.maven.org/maven2/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar;
>  
> - 
> dest="${lib}/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar"
>  
> +
> + src="http://repo1.maven.org/maven2/commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar;
> + 
> dest="${lib}/commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar"
>   usetimestamp="true" 
>   ignoreerrors="true"/>
> -
> - src="http://repo1.maven.org/maven2/org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.jar;
> -
> dest="${lib}/org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.jar"
> +
> + src="http://repo1.maven.org/maven2/org/apache/commons/commons-lang3/3.3.2/commons-lang3-3.3.2.jar;
> +
> dest="${lib}/org/apache/commons/commons-lang3/3.3.2/commons-lang3-3.3.2.jar"
>  usetimestamp="true"
>  ignoreerrors="true"/>
> -
> - src="http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar;
>  
> - 
> dest="${lib}/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar" 
> +
> + src="http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1.3/commons-logging-1.1.3.jar;
> + 
> dest="${lib}/commons-logging/commons-logging/1.1.3/commons-logging-1.1.3.jar"
>   usetimestamp="true" 
>   ignoreerrors="true"/>
>  
> @@ -296,14 +296,14 @@
>   
> dest="${lib}/commons-digester/commons-digester/1.8.1/commons-digester-1.8.1.jar"
>  
>   usetimestamp="true" 
>   ignoreerrors="true"/>
> -
> - src="http://repo1.maven.org/maven2/commons-beanutils/commons-beanutils/1.8.3/commons-beanutils-1.8.3.jar;
>  
> - 
> dest="${lib}/commons-beanutils/commons-beanutils/1.8.3/commons-beanutils-1.8.3.jar"
>  
> +
> + src="http://repo1.maven.org/maven2/commons-beanutils/commons-beanutils/1.9.2/commons-beanutils-1.9.2.jar;
> + 
> dest="${lib}/commons-beanutils/commons-beanutils/1.9.2/commons-beanutils-1.9.2.jar"
>   usetimestamp="false" 
>   ignoreerrors="true"/>
> -
> - src="http://repo1.maven.org/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.jar;
>  
> - dest="${lib}/commons-codec/commons-codec/1.6/commons-codec-1.6.jar" 
> +
> + src="http://repo1.maven.org/maven2/commons-codec/commons-codec/1.9/commons-codec-1.9.jar;
> + dest="${lib}/commons-codec/commons-codec/1.9/commons-codec-1.9.jar"
>   usetimestamp="true" 
>   ignoreerrors="true"/>
>  
> @@ -412,7 +412,7 @@
>   usetimestamp="true" 
>   ignoreerrors="true"/>
>  
> - src="http://repo1.maven.org/maven2/org/easymock/easymock/3.1/easymock-3.2.jar;
>  
> + 

Re: [VOTE] Release Apache Commons FileUpload 1.3.2 based on RC1

[Oliver Heger]

Build (maven) works fine with Java 1.5 and 1.8. Site looks good.

The binary distribution is a bit different from other Commons releases:
It only contains the jar in a lib subfolder (no source or javadoc jar),
and the release notes are missing. But I don't think this is blocking.

So +1

Oliver

My environment:

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: C:\data\dev\tools\apache-maven-3.3.9\bin\..
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_66\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"

Am 23.05.2016 um 17:23 schrieb Benedikt Ritter:
> It has been a long time since the last release of Apache Commons
> FileUpload, so I'd like to release Apache Commons FileUpload 1.3.2 based on
> RC1.
> 
> Apache Commons FileUpload 1.3.2 RC1 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/fileupload (rev 13750)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1173/commons-fileupload/commons-fileupload/1.3.2/
> 
> These are the Maven artifacts and their hashes
> 
> commons-fileupload-1.3.2-javadoc.jar
> (SHA1: 12bbb300a1b61e038defb1dee85e8302d6f1bbaa)
> commons-fileupload-1.3.2-sources.jar
> (SHA1: 23996750d5a80dc74dad55633c2a0f3db91462cb)
> commons-fileupload-1.3.2-test-sources.jar
> (SHA1: 2df285ad143910759a3763fcec0cd58e8525d881)
> commons-fileupload-1.3.2-tests.jar
> (SHA1: 310e3713308073a0392be30c129b55e872fe48f6)
> commons-fileupload-1.3.2,jar
> (SHA1: 5d7491ed6ebd02b6a8d2305f8e6b7fe5dbd95f72)
> commons-fileupload-1.3.2.pom
> (SHA1: a4c3e5d590c2e83bba42768c5b5fbef43219b5c4)
> 
> Details of the change since 1.3.1 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/fileupload/RELEASE-NOTES.txt
> 
> http://home.apache.org/~britter/commons/fileupload-1.3.2-rc1/changes-report.html
> 
> I have tested this with:
>   JDK 1.6 and Maven 3.2.5
>   JDK 1.7 and Maven 3.3.9
>   JDK 1.8 and Maven 3.3.9
> Note that commons-fileupload should be JDK 1.5 compatible, but I don't have
> a JDK 1.5 installation on my MacBook. If someone could check the build with
> JDK 1.5, that would be great!
> 
> The tag is here:
> 
> https://svn.apache.org/repos/asf/commons/proper/fileupload/tags/FILEUPLOAD_1_3_2_RC1
>  (rev 1745203)
> 
> Site:
>   http://home.apache.org/~britter/commons/fileupload-1.3.2-rc1/
> (note some *relative* links are broken and the 1.3.2 directories are not
> yet created - these will be OK once the site is deployed)
> 
> Clirr Report (compared to 1.3):
> 
> http://home.apache.org/~britter/commons/fileupload-1.3.2-rc1/clirr-report.html
> (note that the API additions have been introduced in 1.3.1 not in 1.3.2)
> 
> RAT Report:
> 
> http://home.apache.org/~britter/commons/fileupload-1.3.2-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 than 72 hours from now,
> i.e. sometime after 17:30 CEST 26-May 2016
> 
> [ ] +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

Re: [VOTE] Release Configuration 2.1 based on RC1

[Oliver Heger]

/repository/dom4j/dom4j/1.1/dom4j-1.1.jar
> [ERROR] urls[61] =
> file:/C:/Users/ggregory/.m2/repository/sslext/sslext/1.2-0/sslext-1.2-0.jar
> [ERROR] urls[62] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/struts/struts-core/1.3.8/struts-core-1.3.8.jar
> [ERROR] urls[63] =
> file:/C:/Users/ggregory/.m2/repository/antlr/antlr/2.7.2/antlr-2.7.2.jar
> [ERROR] urls[64] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/struts/struts-taglib/1.3.8/struts-taglib-1.3.8.jar
> [ERROR] urls[65] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/struts/struts-tiles/1.3.8/struts-tiles-1.3.8.jar
> [ERROR] urls[66] =
> file:/C:/Users/ggregory/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar
> [ERROR] urls[67] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/maven/doxia/doxia-integration-tools/1.6/doxia-integration-tools-1.6.jar
> [ERROR] urls[68] =
> file:/C:/Users/ggregory/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> [ERROR] urls[69] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
> [ERROR] urls[70] =
> file:/C:/Users/ggregory/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
> [ERROR] urls[71] =
> file:/C:/Users/ggregory/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
> [ERROR] urls[72] =
> file:/C:/Users/ggregory/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.15/plexus-utils-3.0.15.jar
> [ERROR] urls[73] =
> file:/C:/Users/ggregory/.m2/repository/org/mortbay/jetty/jetty/6.1.25/jetty-6.1.25.jar
> [ERROR] urls[74] =
> file:/C:/Users/ggregory/.m2/repository/org/mortbay/jetty/servlet-api/2.5-20081211/servlet-api-2.5-20081211.jar
> [ERROR] urls[75] =
> file:/C:/Users/ggregory/.m2/repository/org/mortbay/jetty/jetty-util/6.1.25/jetty-util-6.1.25.jar
> [ERROR] urls[76] =
> file:/C:/Users/ggregory/.m2/repository/commons-lang/commons-lang/2.5/commons-lang-2.5.jar
> [ERROR] urls[77] =
> file:/C:/Users/ggregory/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent:
> null]]
> [ERROR]
> [ERROR] -
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
> 
> G
> 
> On Wed, Jul 27, 2016 at 3:12 AM, Benedikt Ritter <brit...@apache.org> wrote:
> 
>> Hello Oliver,
>>
>> Minor nit: Release notes talk about "Commons Configuration Package". I
>> think this should be Apache Commons Configuration.
>>
>> Signs and hashes look good.
>> Website looks good.
>>
>> The build fails with:
>>
>> $ mvn -v
>> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
>> 2014-12-14T18:29:23+01:00)
>> Maven home: /usr/local/Cellar/maven/3.2.5/libexec
>> Java version: 1.6.0_65, vendor: Apple Inc.
>> Java home: /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>> Default locale: de_DE, platform encoding: MacRoman
>> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>>
>> Here is the log output of mvn clean install [1].
>> It looks like the checkstyle plugin version used in the build does not work
>> with Java 6. Since this release should be compatible to Java 6 I consider
>> this blocking. TO make this work we will have to downgrade checkstyle.
>>
>> So my vote is -1 :-(
>>
>> Java 7 and Java 8 builds work fine.
>>
>> Benedikt
>>
>> [1] https://paste.apache.org/gvBS
>>
>> Oliver Heger <oliver.he...@oliver-heger.de> schrieb am So., 24. Juli 2016
>> um 22:31 Uhr:
>>
>>> Hi all,
>>>
>>> there have been a number of bug fixes and also some new features for
>>> [configuration] since version 2.0 has been released. Those should be
>>> made available to the public. This is the vote for the 2.1 release.
>>>
>>> Configuration 2.1 RC1 is available for review here:
>>> https://dist.apache.org/repos/dist/dev/commons/configuration
>>> (revision 14509)
>>>
>>> Maven artifacts are here:
>>>
>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1186/
>>>
>>>

[VOTE] Release Configuration 2.1 based on RC1

[Oliver Heger]

Hi all,

there have been a number of bug fixes and also some new features for
[configuration] since version 2.0 has been released. Those should be
made available to the public. This is the vote for the 2.1 release.

Configuration 2.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/configuration
(revision 14509)

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1186/

Details of changes since 2.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt

https://home.apache.org/~oheger/configuration-2.1-rc1/changes-report.html

Here is the tag:

http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC1
(revision 1753948)

Site:
   https://home.apache.org/~oheger/configuration-2.1-rc1/
(note some links in the menu are not yet working)

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

Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now, i.e. after 2030
GMT 27-Jul 2016

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

Thanks!
Oliver



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

[VOTE] Release Configuration 2.1 based on RC2

[Oliver Heger]

Hi all,

after the failed vote for RC1 a new RC has been created. The only
difference is that the checkstyle plugin has been downgraded which
should allow building the project on Java 1.6.

Configuration 2.1 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/configuration
(revision 14582)

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1194/

Details of changes since 2.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt

https://home.apache.org/~oheger/configuration-2.1-rc2/changes-report.html

Here is the tag:

http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC2
(revision 1754628)

Site:
   https://home.apache.org/~oheger/configuration-2.1-rc2/
(note some links in the menu are not yet working)

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

Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now, i.e. after 2000
GMT 02-Aug-2016

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

Thanks!
Oliver



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

[configuration] Checkstyle settings

[Oliver Heger]

Hi,

in revision 1742698 the checkstyle configuration has been changed. The
log says "fixed checkstyle violations, updated to latest version of
checkstyle-maven-plugin, ensure correct checkstyle configuration is
applied in all cases".

I think with the new configuration checkstyle is now run on every mvn
install and causes the build to fail if there are checkstyle errors.
This is probably not what we want. What was the reason for this update,
i.e. under which circumstances was an incorrect checkstyle configuration
used?

Thanks
Oliver

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

Re: [configuration] Checkstyle settings

[Oliver Heger]

Am 31.07.2016 um 22:24 schrieb Matt Sicker:
> Fixing all the checkstyle errors first is kind of a prerequisite to
> enabling it by default.
> 
> On 31 July 2016 at 15:10, Charles Honton <c...@honton.org> wrote:
> 
>> Why wouldn’t we want build to fail early if incorrect style is used?

In this special case, the build was broken on JDK 1.6 which is blocking
the configuration 2.1 release.

In general, IMHO it is too strict to let the build fail because a
bracket is set incorrectly or something like this. It is fine if this
generates a warning, and these warnings can be fixed before a release.
But I do not want to be forced to fix all style violations at any time.
Especially, as such violations will creep in nevertheless (somebody does
a quick commit without running the full build) and then cause problems
in the future.

Oliver

>>
>> chas
>>
>>> On Jul 31, 2016, at 11:09 AM, Oliver Heger <oliver.he...@oliver-heger.de>
>> wrote:
>>>
>>> Hi,
>>>
>>> in revision 1742698 the checkstyle configuration has been changed. The
>>> log says "fixed checkstyle violations, updated to latest version of
>>> checkstyle-maven-plugin, ensure correct checkstyle configuration is
>>> applied in all cases".
>>>
>>> I think with the new configuration checkstyle is now run on every mvn
>>> install and causes the build to fail if there are checkstyle errors.
>>> This is probably not what we want. What was the reason for this update,
>>> i.e. under which circumstances was an incorrect checkstyle configuration
>>> used?
>>>
>>> Thanks
>>> Oliver
>>>
>>> -
>>> 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 additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release DBCP 2.2 based on RC1

[Oliver Heger]

Build works fine with Java 1.7 and 1.8 on Windows 10. Artifacts and site
look good.

+1, great work!

Oliver

Am 31.07.2016 um 00:15 schrieb Matt Sicker:
> We have fixed quite aWe have fixed quite a few bugs and added some
> significant enhancements since DBCP 2.1.1 was released, so I would like to
> release DBCP 2.2.
> 
> This is my first release on Apache Commons, so please take a close look at
> everything as it's been almost two years since I've been an RM for any
> Apache project. There is a known problem already that I committed some
> things to trunk before making a release  branch, so the current trunk has
> some 2.2 release notes and readme files already which may cause confusion
> until it's released.
> 
> DBCP 2.2 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/DBCP_2_2_RC1/ (svn
> revision 14584)
> 
> The tag is here:
> https://svn.apache.org/repos/asf/commons/proper/dbcp/tags/DBCP_2_2_RC1/
> (svn revision 1754631)
> N.B. the SVN revision is required because SVN tags are not immutable.
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1193/
> 
> These are the Maven artifacts and their hashes (sha256)
> 
> 5fd62ab54872dda88ff0643fe9fe82be39125a0f7712537b3516fa6dcb2fec91
> commons-dbcp2-2.2.jar
> c3983942c3aecd642f76631657789d09fbf63142d0f570fb32925fad65ba6a93
> commons-dbcp2-2.2-javadoc.jar
> 6f5d2087b1198adefbfe2006a9225643c07c9244dc64686895acb2358aedf2d5
> commons-dbcp2-2.2-sources.jar
> 610674620699b5012fdb593b465dce629757dbc1127d68147f0b864b7dd2
> commons-dbcp2-2.2-tests.jar
> ad8341241fa105d26be9508142469881a016959c8d94d6b283cfe1c43d5b9768
> commons-dbcp2-2.2-test-sources.jar
> 
> I have tested this with JDK 1.7 (IcedTea 2.6.6) (Parabola GNU/Linux-libre
> build 7.u101_2.6.6-1.parabola1-x86_64) and 1.8 (build 1.8.0_102-b14), using
> Maven 3.3.9
> 
> Details of changes since 2.1.1 are in the release notes:
> 
> https://svn.apache.org/repos/asf/commons/proper/dbcp/tags/DBCP_2_2_RC1/RELEASE-NOTES.txt
> http://musigma.org/dbcp/changes-report.html
> 
> Site:
> http://musigma.org/dbcp/
>   (note some *relative* links are broken and the 2.2 directories are
>   not yet created - these will be OK once the site is deployed)
>   (also note that I had to upload this to GitHub instead of home.apache.org
> due to technical problems; see https://github.com/jvz/dbcp for source)
> 
> Clirr Report (compared to 2.1.1):
> http://musigma.org/dbcp/clirr-report.html
> 
> Clirr report looks pretty uneventful.
> 
> RAT Report:
> http://musigma.org/dbcp/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. 02-Aug-16 in the evening.
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> 
> --
> Matt Sicker 
> 

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

Re: [VOTE] Release Configuration 2.1 based on RC2

[Oliver Heger]

Am 01.08.2016 um 11:04 schrieb Dennis Kieselhorst:
> Hi Benedikt!
> 
>> The build log is here [1]. It looks like some generated classes are checked
>> by checkstyle which causes the build to fail. The build works with Java 7
>> and Java 8. So my vote again is -1 because I think mvn clean install should
>> work with the minimum required JDK out of the box. Sorry.
>>
> That's strange, I don't see why it should behave differently. Anyway
> I've added an exclude for it (this was already done for rat and clirr).
> This time I installed the same versions you used to build it, so next
> time it should be successful. Sorry for being lazy last time...

Many thanks, Dennis.

I see the checkstyle plugin has a failOnViolation flag which is *true*
per default. Should we set it to *false* (this would be my preference).

I will leave the vote open for now. To make it clear: There is no
problem with the artifacts, they are fully compatible with Java 1.6.
There is only an issue when building with 1.6 which should not affect
many users.

However, I am skeptical whether this vote will pass.

Oliver

> 
> Regards
> Dennis
> 
> -
> 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

[VOTE] Release Configuration 2.1 based on RC3

[Oliver Heger]

Hi all,

after the failed votes for RC1 and RC2 a new RC has been created. There
has been further tweaking of the checkstyle configuration to solve build
problems on Java 1.6.

Configuration 2.1 RC3 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/configuration
(revision 14770)

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1197/

Details of changes since 2.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt

https://home.apache.org/~oheger/configuration-2.1-rc3/changes-report.html

Here is the tag:

http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC3
(revision 1755836)

Site:
   https://home.apache.org/~oheger/configuration-2.1-rc3/
(note some links in the menu are not yet working)

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

Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now, i.e. after 2000
GMT 14-Aug-2016

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

Thanks!
Oliver



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

Re: [configuration] Checkstyle settings

[Oliver Heger]

Hi,

Am 10.08.2016 um 16:05 schrieb Raviteja Lokineni:
> Do you guys need any help in this? I can volunteer my time to help push
> this release, just let me know what needs to be done.

thank you for the offering.

I think, after the latest fix of Dennis, the codebase is now ready to
cut another RC. This can only be done by a committer. I was pretty busy
the last days, but the next RC is now on top of my todo list. So I hope
that I can call for another vote soon.

Oliver

> 
> On Sun, Aug 7, 2016 at 10:12 AM, Dennis Kieselhorst <d...@apache.org> wrote:
> 
>> Am 06.08.2016 um 17:51 schrieb Emmanuel Bourg:
>>> Le 2/08/2016 à 21:17, Oliver Heger a écrit :
>>>
>>>> Well, for me style is not that important. (We cannot even agree on a
>>>> common style for the Commons project.) Therefore, seeing the violations
>>>> in the report is sufficient for me.
>>> +1, the build shouldn't fail due to style issues.
>>>
>> Ok, failOnViolation is now set to false.
>>
>> Regards
>> Dennis
>>
>> -
>> 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 Configuration 2.1 based on RC3

[Oliver Heger]

Am 13.08.2016 um 22:29 schrieb Gary Gregory:
> I would support another RC that clearly documents what the requirements are
> for different parts of the build.

And what would make the big difference to adapted documentation on the side?

Gary, I fail to understand your motivation. In the past you stated
frequently that our release process is a PITA and you keep repeating the
RERO mantra. But now you make the release process even more of a PITA,
and you effectively block a release that has been asked for by users
multiple times.

I think your behavior causes harm to our users and this community as it
generates a lot of frustration. Please reconsider your -1 vote.

Oliver

> 
> Then IMO we should switch trunk to Java 7.
> 
> Gary
> 
> On Aug 13, 2016 12:37 PM, "Oliver Heger" <oliver.he...@oliver-heger.de>
> wrote:
> 
>>
>>
>> Am 12.08.2016 um 20:11 schrieb Gary Gregory:
>>> On Fri, Aug 12, 2016 at 10:24 AM, Dennis Kieselhorst <d...@apache.org>
>>> wrote:
>>>
>>>> Am 12.08.2016 um 01:18 schrieb Gary Gregory:
>>>>> -1
>>>>>
>>>>> From src zip: ASC, MD5, SHA1 OK.
>>>>>
>>>>> Building with:
>>>>>
>>>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>>> 2013-02-19
>>>>> 05:51:28-0800)
>>>>> Maven home: E:\Java\apache-maven-3.0.5
>>>>> Java version: *1.6.0_45*, vendor: Sun Microsystems Inc.
>>>>> Java home: E:\Program Files\Java\jdk1.6.0_45\jre
>>>>> Default locale: en_US, platform encoding: Cp1252
>>>>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>>>>>
>>>> Is it really necessary that the site build is possible with JDK 1.6?
>>>
>>>
>>> For me, keeping it simple is nice. If we say we have different
>> requirements
>>> for building jars vs. building the site, we are making our lives more
>>> difficult IMO.
>>
>> Okay, I have no interest in fixing the site build on Java 1.6 because I
>> do not think it is worth the effort. I belief that not many users will
>> build the site, and even less will do this on a JDK 1.6. It may also
>> well be the case that it is not possible to come to a solution which
>> supports both Java 1.6 and 1.8.
>>
>> So from my PoV we have the following options regarding this release:
>>
>> a) Accept the RC as is and ignore this issue.
>>
>> b) Add a note to the building documentation that the site build requires
>> a minimum JDK of 1.7. This is a change of the site and does not require
>> another RC.
>>
>> c) Switch to JDK 1.7 for [configuration]. I do not think that this is a
>> good solution because then all Java 6 users are out of the game for no
>> good reason.
>>
>> d) I step back as RM and make room for more capable people.
>>
>> Please tell me your preference.
>>
>> Oliver
>>
>>>
>>> Gary
>>>
>>>
>>>> I
>>>> checked the history and Oliver updated the findbugs-plugin with comment
>>>> "The site build now works with Java 1.8.". Site build with JDK 1.8 works
>>>> fine for me. I assume problems problems, if we downgrade it again and
>>>> would prefer that it works with latest JDK version.
>>>>
>>>> Regards
>>>> Dennis
>>>>
>>>> -
>>>> 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 additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Configuration 2.1 based on RC3

[Oliver Heger]

Am 12.08.2016 um 01:19 schrieb Gary Gregory:
> The error was building with 'mvn clean site'.

Can you build the site successfully with a JDK >= 7?

Oliver

> 
> Gary
> 
> On Thu, Aug 11, 2016 at 4:18 PM, Gary Gregory <garydgreg...@gmail.com>
> wrote:
> 
>> -1
>>
>> From src zip: ASC, MD5, SHA1 OK.
>>
>> Building with:
>>
>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
>> 05:51:28-0800)
>> Maven home: E:\Java\apache-maven-3.0.5
>> Java version: *1.6.0_45*, vendor: Sun Microsystems Inc.
>> Java home: E:\Program Files\Java\jdk1.6.0_45\jre
>> Default locale: en_US, platform encoding: Cp1252
>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>>
>> Gives me:
>>
>> [INFO] --- maven-checkstyle-plugin:2.15:check (default) @
>> commons-configuration2 ---
>> [INFO]
>> [INFO] <<< cobertura-maven-plugin:2.7:cobertura-integration-test @
>> commons-configuration2 <<<
>> [INFO] artifact org.apache.commons:commons-configuration2: checking for
>> updates from central
>> [INFO] Fork Value is true
>>  [java] java.lang.UnsupportedClassVersionError:
>> edu/umd/cs/findbugs/FindBugs2 : Unsupported major.minor version 51.0
>>  [java] at java.lang.ClassLoader.defineClass1(Native Method)
>>  [java] at java.lang.ClassLoader.defineClassCond(ClassLoader.
>> java:631)
>>  [java] at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
>>  [java] at java.security.SecureClassLoader.defineClass(
>> SecureClassLoader.java:141)
>>  [java] at java.net.URLClassLoader.defineClass(URLClassLoader.
>> java:283)
>>  [java] at java.net.URLClassLoader.access$000(URLClassLoader.
>> java:58)
>>  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
>>  [java] at java.security.AccessController.doPrivileged(Native
>> Method)
>>  [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:
>> 190)
>>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>  [java] at sun.misc.Launcher$AppClassLoader.loadClass(
>> Launcher.java:301)
>>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>  [java] Could not find the main class: edu.umd.cs.findbugs.FindBugs2.
>> Program will exit.
>>  [java] Exception in thread "main"
>> [INFO] 
>> 
>> [INFO] BUILD FAILURE
>> [INFO] 
>> 
>> [INFO] Total time: 2:18.007s
>> [INFO] Finished at: Thu Aug 11 16:09:43 PDT 2016
>> [INFO] Final Memory: 54M/259M
>> [INFO] 
>> 
>> [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-site-plugin:3.4:site
>> (default-site) on project commons-configuration2: Execution default-site of
>> goal org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Java
>> returned: 1 -> [Help
>> 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
>> PluginExecutionException
>>
>>
>> :-(
>>
>> Gary
>>
>>
>> On Thu, Aug 11, 2016 at 1:02 PM, Oliver Heger <
>> oliver.he...@oliver-heger.de> wrote:
>>
>>> Hi all,
>>>
>>> after the failed votes for RC1 and RC2 a new RC has been created. There
>>> has been further tweaking of the checkstyle configuration to solve build
>>> problems on Java 1.6.
>>>
>>> Configuration 2.1 RC3 is available for review here:
>>> https://dist.apache.org/repos/dist/dev/commons/configuration
>>> (revision 14770)
>>>
>>> Maven artifacts are here:
>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1197/
>>>
>>> Details of changes since 2.0 are in the release notes:
>>>
>>> https://dist.apache.org/repos/dist/dev/commons/configuration
>>> /RELEASE-NOTES.txt
>>>
>>> https://home.apache.org/~oheger/configuration-2.1-rc3/changes-report.html
>>&

Re: [VOTE] Release Configuration 2.1 based on RC3

[Oliver Heger]

Am 12.08.2016 um 20:11 schrieb Gary Gregory:
> On Fri, Aug 12, 2016 at 10:24 AM, Dennis Kieselhorst 
> wrote:
> 
>> Am 12.08.2016 um 01:18 schrieb Gary Gregory:
>>> -1
>>>
>>> From src zip: ASC, MD5, SHA1 OK.
>>>
>>> Building with:
>>>
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>> 2013-02-19
>>> 05:51:28-0800)
>>> Maven home: E:\Java\apache-maven-3.0.5
>>> Java version: *1.6.0_45*, vendor: Sun Microsystems Inc.
>>> Java home: E:\Program Files\Java\jdk1.6.0_45\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>>>
>> Is it really necessary that the site build is possible with JDK 1.6?
> 
> 
> For me, keeping it simple is nice. If we say we have different requirements
> for building jars vs. building the site, we are making our lives more
> difficult IMO.

Okay, I have no interest in fixing the site build on Java 1.6 because I
do not think it is worth the effort. I belief that not many users will
build the site, and even less will do this on a JDK 1.6. It may also
well be the case that it is not possible to come to a solution which
supports both Java 1.6 and 1.8.

So from my PoV we have the following options regarding this release:

a) Accept the RC as is and ignore this issue.

b) Add a note to the building documentation that the site build requires
a minimum JDK of 1.7. This is a change of the site and does not require
another RC.

c) Switch to JDK 1.7 for [configuration]. I do not think that this is a
good solution because then all Java 6 users are out of the game for no
good reason.

d) I step back as RM and make room for more capable people.

Please tell me your preference.

Oliver

> 
> Gary
> 
> 
>> I
>> checked the history and Oliver updated the findbugs-plugin with comment
>> "The site build now works with Java 1.8.". Site build with JDK 1.8 works
>> fine for me. I assume problems problems, if we downgrade it again and
>> would prefer that it works with latest JDK version.
>>
>> Regards
>> Dennis
>>
>> -
>> 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 BCEL 6.0 based on RC7

[Oliver Heger]

Because of the failing test I also feel a bit uneasy, but nevertheless I
am +1: It is only a test class, the problem occurs only in a specific
setup, it is already fixed in trunk, and the release is really overdue.

Thanks
Oliver

Am 05.07.2016 um 11:16 schrieb Benedikt Ritter:
> This vote is still pending and nobody has voted so far. Please review this
> RC and cast your votes!
> 
> Thank you!
> Benedikt
> 
> Benedikt Ritter  schrieb am Sa., 2. Juli 2016 um
> 20:52 Uhr:
> 
>> Hi,
>>
>> I'd like to release Apache Commons BCEL 6.0 based on RC7. Changes compared
>> to RC6 are:
>>
>> - restored binary compatibility to a greater degree
>> - fixed issue BCEL-262
>>
>> BCEL 6.0 RC7 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/bcel/ (svn revision 14251)
>>
>> The tag is here:
>> http://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0_RC7/
>> (svn revision 1751084)
>>
>> Maven artifacts are here:
>> https://repository.apache.org/content/repositories/orgapachecommons-1181/org/apache/bcel/bcel/6.0/
>>
>> These are the Maven artifacts and their hashes
>>
>> bcel-6.0-javadoc.jar
>>   (SHA1: f1e1534867a901b9ba4884e5805317635c324589)
>> bcel-6.0-sources.jar
>>   (SHA1: 9ba3b50aa95289d01ec119b60be68eb4c608ba1d)
>> bcel-6.0-test-sources.jar
>>   (SHA1: 484b29d3a73fbe0c103d85965c4fd22e6253f545)
>> bcel-6.0-tests.jar
>>   (SHA1: f8b5857f3245e10548ef29cf7006c045b913a199)
>> bcel-6.0.jar
>>   (SHA1: fe1ecaf2ba3b1f9f18cdde4f13943e3ccc1d5e69)
>> bcel-6.0.pom
>>   (SHA1: ea17ee1b2c28804437212970ea2d273efeb3807e)
>>
>> I have tested this with JDK 7, 8 using Maven 3.3.9.
>>
>> Details of changes since 1.1 are in the release notes:
>>   https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-NOTES.txt
>>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/changes-report.html
>>
>> Site:
>>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/
>> (note some *relative* links are broken and the 6.0 directories are not yet
>> created - these will be OK once the site is deployed)
>>
>> Clirr Report (compared to 5.2):
>>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/clirr-report.html
>>
>> Note that Clirr reports several errors.
>> These are considered OK for the reasons stated below.
>> These exceptions are also noted in the Changes and Release Notes.
>>
>> Errors reported:
>> - methods added to org.apache.bcel.classfile.Visitor interface: OK because
>> that does not affect binary compatibility.
>> - Removed java.io.Serializable from all classes: OK, because we don't
>> expect anybody to rely on serialization for BCEL classes
>> - Return type of method 'public java.lang.Object getElementAt(int)' has
>> been changed to java.lang.String in class
>> org.apache.bcel.verifier.VerifierFactoryListModel: OK, because this class
>> is part of an UI application and for this reason should only used by Swing.
>>
>> RAT Report:
>>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/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 21:00 CEST 05-July 2016
>>
>> [ ] +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

Re: [VOTE] Release Apache Commons BCEL 6.0 based on RC7

[Oliver Heger]

Hi Gary,

Am 04.07.2016 um 00:55 schrieb Gary Gregory:
> Arg! That looks like an invalid assumption in the test code I wrote. I made
> an adjustment in trunk. Can you try it again from trunk?

the fix works for me. The build from trunk is now successful with Java 1.7.

Oliver

> 
> Thank you,
> Gary
> 
> On Sun, Jul 3, 2016 at 12:39 PM, Oliver Heger <oliver.he...@oliver-heger.de>
> wrote:
> 
>> Ok, here is the full stack trace. The German error message means that
>> the system cannot find the specified file.
>>
>> What kind of registry information do you need?
>>
>> Oliver
>>
>>
>> ---
>> Test set: org.apache.bcel.generic.JDKGenericDumpTestCase
>>
>> ---
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.359
>> sec <<< FAILURE! - in org.apache.bcel.generic.JDKGenericDumpTestCase
>> initializationError(org.apache.bcel.generic.JDKGenericDumpTestCase)
>> Time elapsed: 0.015 sec  <<< ERROR!
>> com.sun.jna.platform.win32.Win32Exception: Das System kann die
>> angegebene Datei nicht finden.
>> at
>>
>> org.apache.bcel.generic.JDKGenericDumpTestCase.findJavaHomesOnWindows(JDKGenericDumpTestCase.java:84)
>> at
>>
>> org.apache.bcel.generic.JDKGenericDumpTestCase.findJavaHomesOnWindows(JDKGenericDumpTestCase.java:77)
>> at
>>
>> org.apache.bcel.generic.JDKGenericDumpTestCase.findJavaHomes(JDKGenericDumpTestCase.java:65)
>> at
>>
>> org.apache.bcel.generic.JDKGenericDumpTestCase.data(JDKGenericDumpTestCase.java:60)
>>
>>
>>
>> Am 03.07.2016 um 17:18 schrieb Gary Gregory:
>>> What are stack traces for the errors? All the tests pass for me on
>> Windows
>>> 7 with this RC. I added some test code to find all Java installs since
>> the
>>> last RC. I see you are on Windows 10, so I am curious as to your
>> failures,
>>> stack traces and windows registry set up.
>>>
>>> Gary
>>> On Jul 3, 2016 7:50 AM, "Oliver Heger" <oliver.he...@oliver-heger.de>
>> wrote:
>>>
>>>> Hi,
>>>>
>>>> when building from the source distribution with both Java 1.7 and 1.8 I
>>>> get the following test failure:
>>>>
>>>> Results :
>>>>
>>>> Tests in error:
>>>>
>>>>
>>>>
>> JDKGenericDumpTestCase.data:60->findJavaHomes:65->findJavaHomesOnWindows:77->findJavaHomesOnWindows:84
>>>> » Win32
>>>>
>>>> Tests run: 102, Failures: 0, Errors: 1, Skipped: 0
>>>>
>>>> Does anybody else see this? I do not remember this failure with the last
>>>> RC. Below is my platform:
>>>>
>>>> c:\data\dev\projects\OpenSource\bcel\bcel-6.0-src>mvn -version
>>>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>>>> 2015-11-10T17:41:47+01:00)
>>>> Maven home: c:\data\dev\tools\apache-maven-3.3.9\bin\..
>>>> Java version: 1.8.0_66, vendor: Oracle Corporation
>>>> Java home: C:\Program Files\Java\jdk1.8.0_66\jre
>>>> Default locale: de_DE, platform encoding: Cp1252
>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
>>>>
>>>> Oliver
>>>>
>>>> Am 02.07.2016 um 20:52 schrieb Benedikt Ritter:
>>>>> Hi,
>>>>>
>>>>> I'd like to release Apache Commons BCEL 6.0 based on RC7. Changes
>>>> compared
>>>>> to RC6 are:
>>>>>
>>>>> - restored binary compatibility to a greater degree
>>>>> - fixed issue BCEL-262
>>>>>
>>>>> BCEL 6.0 RC7 is available for review here:
>>>>> https://dist.apache.org/repos/dist/dev/commons/bcel/ (svn revision
>>>> 14251)
>>>>>
>>>>> The tag is here:
>>>>> http://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0_RC7/
>>>> (svn
>>>>> revision 1751084)
>>>>>
>>>>> Maven artifacts are here:
>>>>>
>>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1181/org/apache/bcel/bcel/6.0/
>>>>>
>>>>> These are the Maven artifacts and their hashes
>>>>>
>>>>> bcel-6.0-java

Re: [VOTE] Release Apache Commons BCEL 6.0 based on RC8

[Oliver Heger]

Build works fine with Java 1.7 and 1.8 on Windows 10. Artifacts and site
look good.

+1

Oliver

Am 10.07.2016 um 22:57 schrieb Benedikt Ritter:
> Hi all,
> 
> hopefully the final RC for releasing Apache Commons BCEL 6.0 :-) Changes
> since RC7:
> 
> - fixed failing build on Windows plattforms
> - corrected fix for BCEL-262
> 
> Apache Commons BCEL 6.0 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/bcel (rev 14344)
> 
> The tag is here:
>   https://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0_RC8
>  (rev 1752118)
> 
> Maven artifacts:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1183/org/apache/bcel/bcel/6.0/
> 
> Maven artifact hashes:
> 
> bcel-6.0-test-sources.jar
> (SHA1: 30ba969d603b676929b69228ad0f2a4fc1c9c830)
> bcel-6.0.pom
> (SHA1: aff6c560d92df15a207247c5b0293bb734389094)
> bcel-6.0.jar
> (SHA1: 7d08bcac4832f81467d3e2ca5bd58ad627288656)
> bcel-6.0-tests.jar
> (SHA1: 3536d25398f6f6ac22deb9e446515056191661f7)
> bcel-6.0-javadoc.jar
> (SHA1: e47a109aa7416329a9970f0900136cb355af8ac8)
> bcel-6.0-sources.jar
> (SHA1: 206dfd32271b9b0150d8211070e5dbbe69cf5154)
> 
> I've tested with Java 7 & 8 using Maven 3.3.9
> 
> Details of changes since 5.2 are in the release notes:
>   https://dist.apache.org/repos/dist/dev/commons/bcel//RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/bcel/6.0-RC8/changes-report.html
> 
> Site:
>   http://home.apache.org/~britter/commons/bcel/6.0-RC8
> (note some *relative* links are broken and the 6.0 directories are not yet
> created - these will be OK once the site is deployed)
> 
> Clirr Report (compared to 5.2):
>   http://home.apache.org/~britter/commons/bcel/6.0-RC8/clirr-report.html
> 
> Note that Clirr reports several errors.
> These are considered OK for the reasons stated below.
> These exceptions are also noted in the Changes and Release Notes.
> 
> Errors reported:
> - methods added to org.apache.bcel.classfile.Visitor interface: OK because
> that does not affect binary compatibility.
> - Removed java.io.Serializable from all classes: OK, because we don't
> expect anybody to rely on serialization for BCEL classes
> - Return type of method 'public java.lang.Object getElementAt(int)' has
> been changed to java.lang.String in class
> org.apache.bcel.verifier.VerifierFactoryListModel:
> OK, because this class is part of an UI application and for this reason
> should only used by Swing.
> 
> RAT Report:
>   http://home.apache.org/~britter/commons/bcel/6.0-RC8/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 23:00 CEST 13-July 2016
> 
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
> 
> Thank you!
> Benedikt
> 

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

Re: [VOTE] Release Configuration 2.1 based on RC2

[Oliver Heger]

Hi,

so do we have a confirmation that the current state in trunk builds
correctly on the problematic platforms? Then I could start preparing
another RC in the next days.

Thanks
Oliver

Am 02.08.2016 um 09:08 schrieb Dennis Kieselhorst:
> Hi Gary!
>> We have a mini-mess here:
>>
>> - checkstyle's check is called from the build and it fails.
>> - Did it ever work?
>> - Did it work and then the code degraded between the last release and this
>> code base? The 2.0 checkstyle is clean:
>> https://commons.apache.org/proper/commons-configuration/checkstyle.html
>> - Have the checkstyle default rules changed between the checkstyle version
>> used in 2.0 and now?
>> - Have the checkstyle custom rules we use changed between the checkstyle
>> version used in 2.0 and now?
>> - The code could be fixed to match the rules of course.
>>
> The generated code never matched the ruleset and I think it would be
> hart to fix the code generation so I've added an exclude for that. Could
> you please try trunk and see if it's ok for you?
> 
> After that we should build an RC3.
> 
> Regards
> Dennis
> 
> -
> 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 Configuration 2.1 based on RC2

[Oliver Heger]

Am 01.08.2016 um 21:50 schrieb Gary Gregory:
> On Mon, Aug 1, 2016 at 12:38 PM, Oliver Heger <oliver.he...@oliver-heger.de>
> wrote:
> 
>>
>>
>> Am 01.08.2016 um 11:04 schrieb Dennis Kieselhorst:
>>> Hi Benedikt!
>>>
>>>> The build log is here [1]. It looks like some generated classes are
>> checked
>>>> by checkstyle which causes the build to fail. The build works with Java
>> 7
>>>> and Java 8. So my vote again is -1 because I think mvn clean install
>> should
>>>> work with the minimum required JDK out of the box. Sorry.
>>>>
>>> That's strange, I don't see why it should behave differently. Anyway
>>> I've added an exclude for it (this was already done for rat and clirr).
>>> This time I installed the same versions you used to build it, so next
>>> time it should be successful. Sorry for being lazy last time...
>>
>> Many thanks, Dennis.
>>
>> I see the checkstyle plugin has a failOnViolation flag which is *true*
>> per default. Should we set it to *false* (this would be my preference).
>>
>> I will leave the vote open for now. To make it clear: There is no
>> problem with the artifacts, they are fully compatible with Java 1.6.
>> There is only an issue when building with 1.6 which should not affect
>> many users.
>>
>> However, I am skeptical whether this vote will pass.
>>
> 
> Well, yeah, the build should work out of the box. With Java 6 and 7, for
> 'mvn clean site', I get:
> 
> [INFO] --- maven-checkstyle-plugin:2.15:check (default) @
> commons-configuration2 ---
> [INFO] There are 1238 errors reported by Checkstyle 6.1.1 with
> E:\temp\rc\commons-configuration2-2.1-src/conf/checkstyle.xml ruleset.
> [ERROR]
> target\generated-sources\javacc\org\apache\commons\configuration2\plist\ParseException.java[0]
> (javadoc) JavadocPackage: Missing package-info.java file.
> 
> I cannot imagine Java 8 would be any different.

This is indeed strange. I do not see these errors when building with
Java 7 and 8. I have created the web site for the RC that way.

Maybe it depends on the Maven version?

Oliver

> 
> We have a mini-mess here:
> 
> - checkstyle's check is called from the build and it fails.
> - Did it ever work?
> - Did it work and then the code degraded between the last release and this
> code base? The 2.0 checkstyle is clean:
> https://commons.apache.org/proper/commons-configuration/checkstyle.html
> - Have the checkstyle default rules changed between the checkstyle version
> used in 2.0 and now?
> - Have the checkstyle custom rules we use changed between the checkstyle
> version used in 2.0 and now?
> - The code could be fixed to match the rules of course.
> 
> Gary
> 
> 
>> Oliver
>>
>>>
>>> Regards
>>> Dennis
>>>
>>> -
>>> 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 additional commands, e-mail: dev-h...@commons.apache.org

Re: [configuration] Checkstyle settings

[Oliver Heger]

Am 02.08.2016 um 08:54 schrieb Dennis Kieselhorst:
> Am 01.08.2016 um 21:31 schrieb Oliver Heger:
>> Am 31.07.2016 um 22:24 schrieb Matt Sicker:
>>> Fixing all the checkstyle errors first is kind of a prerequisite to
>>> enabling it by default.
>>>
>>> On 31 July 2016 at 15:10, Charles Honton <c...@honton.org> wrote:
>>>
>>>> Why wouldn’t we want build to fail early if incorrect style is used?
>> In this special case, the build was broken on JDK 1.6 which is blocking
>> the configuration 2.1 release.
>>
>> In general, IMHO it is too strict to let the build fail because a
>> bracket is set incorrectly or something like this. It is fine if this
>> generates a warning, and these warnings can be fixed before a release.
>> But I do not want to be forced to fix all style violations at any time.
>> Especially, as such violations will creep in nevertheless (somebody does
>> a quick commit without running the full build) and then cause problems
>> in the future.
>>
> I've changed it after committing with wrong codestyle. Before the
> checkstyle config was just in the reporting section, so only just for
> site generation. When I was running mvn checkstyle:check before my
> commit, I got thousands of violations as a default ruleset was applied.
> 
> Now you immediately see during normal build that something is wrong. Of
> course the build was passing after the change. During the release build
> we just discovered that generated sources were checked as well when
> using Maven 3.2.5 and JDK 1.6, but not checked when using Maven 3.3.9
> and JDK 1.7/ 1.8. This is now fixed by an exclude for the generated sources.
> 
> I prefer that the build fails as warnings are often ignored. If we
> change it, we should at least fail on Jenkins (using a ci profile).

Well, for me style is not that important. (We cannot even agree on a
common style for the Commons project.) Therefore, seeing the violations
in the report is sufficient for me.

Other reports are IMHO more important, e.g. findbugs or RAT (for legal
reasons). Would we also let the build fail when here violations are found?

I fear that such strict rules will also be an obstacle for contributors:
Somebody wants to play with the code, tries something out, and the build
fails because of unrelated stuff.

Oliver

> 
> Regards
> Dennis
> 
> -
> 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 Configuration 2.1 based on RC1

[Oliver Heger]

Hi Benedikt,

Am 28.07.2016 um 08:30 schrieb Benedikt Ritter:
> Hello Oliver,
> 
> Oliver Heger <oliver.he...@oliver-heger.de> schrieb am Mi., 27. Juli 2016
> um 21:30 Uhr:
> 
>> Thanks for the reviews so far.
>>
>> I tested with the Java 1.6 compatibility profile, and here a mvn clean
>> install is successful (using Maven 3.3.9).
>>
> 
> do you use the profile defined in parent pom? Can you paste the exact
> command line your using?

the following command works for me:

mvn clean install -P java-1.6

However, this of course requires that the corresponding profiles are
correctly setup in settings.xml.

Oliver

> 
> 
>>
>> Any proposals which version of the checkstyle plugin would be
>> compatible? Or why does the checkstyle plugin becomes active for a mvn
>> clean install at all?
>>
> 
> I think this is because it is configured as build plugin and as report
> plugin. This way you can run mvn checkstyle:check and you will get the HTML
> report when running mvn site.
> 
> 
>>
>> Personally, I don't have an issue with moving forward to Java 1.7, but
>> would prefer a better reason than "because the checkstyle plugin does
>> not support 1.6 any more".
>>
> 
> Yes. I think we will have to find out how to configure the build for
> running with Java 1.6 or we need to document how to build with Java 1.6 in
> the current state.
> 
> Benedikt
> 
> 
>>
>> Oliver
>>
>> Am 27.07.2016 um 21:04 schrieb Gary Gregory:
>>> Bummer! I have to change my vote from +1 to -1. I used Java 8 to test,
>>> which I should not have. With Java 6, it fails indeed [1].
>>>
>>> I used:
>>>
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
>>> 05:51:28-0800)
>>> Maven home: E:\Java\apache-maven-3.0.5
>>> Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
>>> Java home: E:\Program Files\Java\jdk1.6.0_45\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>>>
>>> Remedy 1: Change plugin versions.
>>> Remedy 2: Update Java requirements from 6 to 7, which I would propose for
>>> 2.2 anyway.
>>>
>>> Gary
>>>
>>> [1] [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
>>> project commons-configuration2: Execution default-site of goal
>>> org.apache.maven.plugins:maven-site-plugin:3.4:site failed: An API
>>> incompatibility was
>>>  encountered while executing
>>> org.apache.maven.plugins:maven-site-plugin:3.4:site:
>>> java.lang.UnsupportedClassVersionError:
>>> org/apache/maven/plugin/checkstyle/CheckstyleReport : Unsupported
>>> major.minor version 51.0
>>> [ERROR] -
>>> [ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.4
>>> [ERROR] strategy =
>>> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
>>> [ERROR] urls[0] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.4/maven-site-plugin-3.4.jar
>>> [ERROR] urls[1] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/org/apache/maven/wagon/wagon-ssh/2.10/wagon-ssh-2.10.jar
>>> [ERROR] urls[2] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/com/jcraft/jsch/0.1.50/jsch-0.1.50.jar
>>> [ERROR] urls[3] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/com/jcraft/jsch.agentproxy.connector-factory/0.0.6/jsch.agentproxy.connector-factory-0.0.6.jar
>>> [ERROR] urls[4] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/com/jcraft/jsch.agentproxy.core/0.0.6/jsch.agentproxy.core-0.0.6.jar
>>> [ERROR] urls[5] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/com/jcraft/jsch.agentproxy.usocket-jna/0.0.6/jsch.agentproxy.usocket-jna-0.0.6.jar
>>> [ERROR] urls[6] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/net/java/dev/jna/jna/3.4.0/jna-3.4.0.jar
>>> [ERROR] urls[7] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/net/java/dev/jna/platform/3.4.0/platform-3.4.0.jar
>>> [ERROR] urls[8] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/com/jcraft/jsch.agentproxy.usocket-nc/0.0.6/jsch.agentproxy.usocket-nc-0.0.6.jar
>>> [ERROR] urls[9] =
>>>
>> file:/C:/Users/ggregory/.m2/repository/com/jcraft/jsch.agentproxy.sshagent/0.0.6/jsch.agentproxy.sshagent-0.0.6.jar
>>> [ER

[CANCELED][VOTE] Release Configuration 2.1 based on RC1

[Oliver Heger]

This vote is canceled because of a problem with the build under Java 1.6.

I will create another RC soon.

Thanks for the reviews.
Oliver

Am 24.07.2016 um 22:31 schrieb Oliver Heger:
> Hi all,
> 
> there have been a number of bug fixes and also some new features for
> [configuration] since version 2.0 has been released. Those should be
> made available to the public. This is the vote for the 2.1 release.
> 
> Configuration 2.1 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/configuration
> (revision 14509)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1186/
> 
> Details of changes since 2.0 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
> 
> https://home.apache.org/~oheger/configuration-2.1-rc1/changes-report.html
> 
> Here is the tag:
> 
> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC1
> (revision 1753948)
> 
> Site:
>https://home.apache.org/~oheger/configuration-2.1-rc1/
> (note some links in the menu are not yet working)
> 
> KEYS:
>   http://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 2030
> GMT 27-Jul 2016
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> Oliver
> 
> 
> 
> -
> 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 BCEL 6.0 based on RC7

[Oliver Heger]

Hi,

when building from the source distribution with both Java 1.7 and 1.8 I
get the following test failure:

Results :

Tests in error:

JDKGenericDumpTestCase.data:60->findJavaHomes:65->findJavaHomesOnWindows:77->findJavaHomesOnWindows:84
» Win32

Tests run: 102, Failures: 0, Errors: 1, Skipped: 0

Does anybody else see this? I do not remember this failure with the last
RC. Below is my platform:

c:\data\dev\projects\OpenSource\bcel\bcel-6.0-src>mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: c:\data\dev\tools\apache-maven-3.3.9\bin\..
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_66\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"

Oliver

Am 02.07.2016 um 20:52 schrieb Benedikt Ritter:
> Hi,
> 
> I'd like to release Apache Commons BCEL 6.0 based on RC7. Changes compared
> to RC6 are:
> 
> - restored binary compatibility to a greater degree
> - fixed issue BCEL-262
> 
> BCEL 6.0 RC7 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/bcel/ (svn revision 14251)
> 
> The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0_RC7/ (svn
> revision 1751084)
> 
> Maven artifacts are here:
> https://repository.apache.org/content/repositories/orgapachecommons-1181/org/apache/bcel/bcel/6.0/
> 
> These are the Maven artifacts and their hashes
> 
> bcel-6.0-javadoc.jar
>   (SHA1: f1e1534867a901b9ba4884e5805317635c324589)
> bcel-6.0-sources.jar
>   (SHA1: 9ba3b50aa95289d01ec119b60be68eb4c608ba1d)
> bcel-6.0-test-sources.jar
>   (SHA1: 484b29d3a73fbe0c103d85965c4fd22e6253f545)
> bcel-6.0-tests.jar
>   (SHA1: f8b5857f3245e10548ef29cf7006c045b913a199)
> bcel-6.0.jar
>   (SHA1: fe1ecaf2ba3b1f9f18cdde4f13943e3ccc1d5e69)
> bcel-6.0.pom
>   (SHA1: ea17ee1b2c28804437212970ea2d273efeb3807e)
> 
> I have tested this with JDK 7, 8 using Maven 3.3.9.
> 
> Details of changes since 1.1 are in the release notes:
>   https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/changes-report.html
> 
> Site:
>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/
> (note some *relative* links are broken and the 6.0 directories are not yet
> created - these will be OK once the site is deployed)
> 
> Clirr Report (compared to 5.2):
>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/clirr-report.html
> 
> Note that Clirr reports several errors.
> These are considered OK for the reasons stated below.
> These exceptions are also noted in the Changes and Release Notes.
> 
> Errors reported:
> - methods added to org.apache.bcel.classfile.Visitor interface: OK because
> that does not affect binary compatibility.
> - Removed java.io.Serializable from all classes: OK, because we don't
> expect anybody to rely on serialization for BCEL classes
> - Return type of method 'public java.lang.Object getElementAt(int)' has
> been changed to java.lang.String in class
> org.apache.bcel.verifier.VerifierFactoryListModel: OK, because this class
> is part of an UI application and for this reason should only used by Swing.
> 
> RAT Report:
>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/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 21:00 CEST 05-July 2016
> 
> [ ] +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

Re: [VOTE] Release Apache Commons BCEL 6.0 based on RC7

[Oliver Heger]

Ok, here is the full stack trace. The German error message means that
the system cannot find the specified file.

What kind of registry information do you need?

Oliver

---
Test set: org.apache.bcel.generic.JDKGenericDumpTestCase
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.359
sec <<< FAILURE! - in org.apache.bcel.generic.JDKGenericDumpTestCase
initializationError(org.apache.bcel.generic.JDKGenericDumpTestCase)
Time elapsed: 0.015 sec  <<< ERROR!
com.sun.jna.platform.win32.Win32Exception: Das System kann die
angegebene Datei nicht finden.
at
org.apache.bcel.generic.JDKGenericDumpTestCase.findJavaHomesOnWindows(JDKGenericDumpTestCase.java:84)
at
org.apache.bcel.generic.JDKGenericDumpTestCase.findJavaHomesOnWindows(JDKGenericDumpTestCase.java:77)
at
org.apache.bcel.generic.JDKGenericDumpTestCase.findJavaHomes(JDKGenericDumpTestCase.java:65)
at
org.apache.bcel.generic.JDKGenericDumpTestCase.data(JDKGenericDumpTestCase.java:60)



Am 03.07.2016 um 17:18 schrieb Gary Gregory:
> What are stack traces for the errors? All the tests pass for me on Windows
> 7 with this RC. I added some test code to find all Java installs since the
> last RC. I see you are on Windows 10, so I am curious as to your failures,
> stack traces and windows registry set up.
> 
> Gary
> On Jul 3, 2016 7:50 AM, "Oliver Heger" <oliver.he...@oliver-heger.de> wrote:
> 
>> Hi,
>>
>> when building from the source distribution with both Java 1.7 and 1.8 I
>> get the following test failure:
>>
>> Results :
>>
>> Tests in error:
>>
>>
>> JDKGenericDumpTestCase.data:60->findJavaHomes:65->findJavaHomesOnWindows:77->findJavaHomesOnWindows:84
>> » Win32
>>
>> Tests run: 102, Failures: 0, Errors: 1, Skipped: 0
>>
>> Does anybody else see this? I do not remember this failure with the last
>> RC. Below is my platform:
>>
>> c:\data\dev\projects\OpenSource\bcel\bcel-6.0-src>mvn -version
>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> 2015-11-10T17:41:47+01:00)
>> Maven home: c:\data\dev\tools\apache-maven-3.3.9\bin\..
>> Java version: 1.8.0_66, vendor: Oracle Corporation
>> Java home: C:\Program Files\Java\jdk1.8.0_66\jre
>> Default locale: de_DE, platform encoding: Cp1252
>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
>>
>> Oliver
>>
>> Am 02.07.2016 um 20:52 schrieb Benedikt Ritter:
>>> Hi,
>>>
>>> I'd like to release Apache Commons BCEL 6.0 based on RC7. Changes
>> compared
>>> to RC6 are:
>>>
>>> - restored binary compatibility to a greater degree
>>> - fixed issue BCEL-262
>>>
>>> BCEL 6.0 RC7 is available for review here:
>>> https://dist.apache.org/repos/dist/dev/commons/bcel/ (svn revision
>> 14251)
>>>
>>> The tag is here:
>>> http://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0_RC7/
>> (svn
>>> revision 1751084)
>>>
>>> Maven artifacts are here:
>>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1181/org/apache/bcel/bcel/6.0/
>>>
>>> These are the Maven artifacts and their hashes
>>>
>>> bcel-6.0-javadoc.jar
>>>   (SHA1: f1e1534867a901b9ba4884e5805317635c324589)
>>> bcel-6.0-sources.jar
>>>   (SHA1: 9ba3b50aa95289d01ec119b60be68eb4c608ba1d)
>>> bcel-6.0-test-sources.jar
>>>   (SHA1: 484b29d3a73fbe0c103d85965c4fd22e6253f545)
>>> bcel-6.0-tests.jar
>>>   (SHA1: f8b5857f3245e10548ef29cf7006c045b913a199)
>>> bcel-6.0.jar
>>>   (SHA1: fe1ecaf2ba3b1f9f18cdde4f13943e3ccc1d5e69)
>>> bcel-6.0.pom
>>>   (SHA1: ea17ee1b2c28804437212970ea2d273efeb3807e)
>>>
>>> I have tested this with JDK 7, 8 using Maven 3.3.9.
>>>
>>> Details of changes since 1.1 are in the release notes:
>>>   https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-NOTES.txt
>>>
>> http://home.apache.org/~britter/commons/bcel/6.0-RC7/changes-report.html
>>>
>>> Site:
>>>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/
>>> (note some *relative* links are broken and the 6.0 directories are not
>> yet
>>> created - these will be OK once the site is deployed)
>>>
>>> Clirr Report (compared to 5.2):
>>>   http://home.apache.org/~britter/commons/bcel/6.0-RC7/clirr-r

[RESULT][VOTE] Release Configuration 2.1 based on RC3

[Oliver Heger]

The vote to release Configuration 2.1 based on RC3 failed with the
following binding votes:

Gary Gregory:   -1
Jörg Schaible:  +1
Oliver Heger:   +1

Oliver  

Am 11.08.2016 um 22:02 schrieb Oliver Heger:
> Hi all,
> 
> after the failed votes for RC1 and RC2 a new RC has been created. There
> has been further tweaking of the checkstyle configuration to solve build
> problems on Java 1.6.
> 
> Configuration 2.1 RC3 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/configuration
> (revision 14770)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1197/
> 
> Details of changes since 2.0 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
> 
> https://home.apache.org/~oheger/configuration-2.1-rc3/changes-report.html
> 
> Here is the tag:
> 
> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC3
> (revision 1755836)
> 
> Site:
>https://home.apache.org/~oheger/configuration-2.1-rc3/
> (note some links in the menu are not yet working)
> 
> KEYS:
>   http://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 2000
> GMT 14-Aug-2016
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> Oliver
> 
> 
> 
> -
> 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 Configuration 2.1 based on RC3

[Oliver Heger]

+1

Oliver

Am 11.08.2016 um 22:02 schrieb Oliver Heger:
> Hi all,
> 
> after the failed votes for RC1 and RC2 a new RC has been created. There
> has been further tweaking of the checkstyle configuration to solve build
> problems on Java 1.6.
> 
> Configuration 2.1 RC3 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/configuration
> (revision 14770)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1197/
> 
> Details of changes since 2.0 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
> 
> https://home.apache.org/~oheger/configuration-2.1-rc3/changes-report.html
> 
> Here is the tag:
> 
> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC3
> (revision 1755836)
> 
> Site:
>https://home.apache.org/~oheger/configuration-2.1-rc3/
> (note some links in the menu are not yet working)
> 
> KEYS:
>   http://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 2000
> GMT 14-Aug-2016
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> Oliver
> 
> 
> 
> -
> 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: [CONFIGURATION] Ready for 2.2 release?

[Oliver Heger]

Am 03.02.2017 um 12:24 schrieb Benedikt Ritter:
> Hi,
> 
> I need some fixes from trunk in one of my projects. Since I’ve not been 
> involved in the development of [CONFIGURATION], I’d like to ask what is 
> blocking the 2.2 release and whether there is someone willing to RM.
> 

AFAICT, there is nothing blocking a new release. In contrary, it would
be nice to get the current set of fixes out.

Regarding RM, I am pretty busy myself. I can put it on my TODO list, but
cannot say when I come to it.

Oliver

> Regards,
> 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 Commons Text 1.0-beta-1 based on RC4

[Oliver Heger]

Hi Rob,

all my points from the previous RC have been addressed.

+1

Great work!

One minor thing I noticed: AFAIK, the md5 hashes have to be added to the
files in the distribution area.

Oliver

Am 30.01.2017 um 15:14 schrieb Rob Tompkins:
> Hello all,
> 
> This is a [VOTE] for releasing Apache Commons Text 1.0-beta-1 (from RC4).
> 
> Tag name:
>commons-text-1.0-beta-1-RC4 (signature can be checked from git using 'git 
> tag -v')
> 
> Tag URL:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=65e4314fbd6c3a8f5c248d07a4ccffc1f0ea8bb9
> 
> Commit ID the tag points at:
>65e4314fbd6c3a8f5c248d07a4ccffc1f0ea8bb9
> 
> Site:
>http://home.apache.org/~chtompki/commons-text-1.0-beta-1-RC4
> 
> Distribution files (committed at revision 18041):
>https://dist.apache.org/repos/dist/dev/commons/text/
> 
> Distribution files hashes (SHA1):
>commons-text-1.0-beta-1-bin.tar.gz
>(SHA: dcedb6acc9e8dee75ef9ebefc3a03d20df1d84af)
>commons-text-1.0-beta-1-bin.zip
>(SHA1: b1fa8083bfdcec354a97c23468aa63082990febe)
>commons-text-1.0-beta-1-src.tar.gz
>(SHA1: 06e7bee6a1a710fb2a68472bbbd3209bdc66802c)
>commons-text-1.0-beta-1-src.zip
>(SHA1: 62f405f55689526ca87fd228ed4ae4a4cf4ad107)
> 
> These are the Maven artifacts and their hashes:
>commons-text-1.0-beta-1-javadoc.jar
>(SHA1: 771928f5f5439dbf75d857b4a8da83646ba854e8)
>commons-text-1.0-beta-1-sources.jar
>(SHA1: 104e0d8fe8791d7e6f0653fee406150e6f80ee0e)
>commons-text-1.0-beta-1-test-sources.jar
>(SHA1: 0e0b2ea171d8f82c4775b0e472c41b316052de8f)
>commons-text-1.0-beta-1-tests.jar
>(SHA1: 664d9d71be733cc8240a4164e6a3971fc9e95578)
>commons-text-1.0-beta-1.jar
>(SHA1: 6ef0390cf936f21e07ed47f34ba7eab0d918606b)
>commons-text-1.0-beta-1.pom
>(SHA1: 7b65ac70d36c5acf3bcad87ed2df9e7eba111726)
> 
> KEYS file to check signatures:
>http://www.apache.org/dist/commons/KEYS
> 
> Maven artifacts:
>https://repository.apache.org/content/repositories/orgapachecommons-1234
> 
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
> 
> This vote will be open at least 72 hours, i.e. until 
> 2017-02-02T15:00:00Z
> (this is UTC time).
> 
> 
> Cheers,
> -Rob
> 
> [1] http://apache.org/foundation/voting.html
> -
> 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 JCS 2.1 based on RC1

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. The site build
failed for me with Java 1.8 because of Javadoc errors, but this is not
blocking. Site and artifacts look good.

I noticed that OSGi manifests of jars use the same symbolic bundle name,
e.g. for commons-jcs-core-2.1.jar and
commons-jcs-jcache-openjpa-2.1.jar. This is likely to cause problems in
an OSGi container.

In total I am +1 for the release.

Oliver

Am 05.02.2017 um 18:24 schrieb Thomas Vandahl:
> I would like to release the [jcs] component to resolve some bugs
> 
> Apache Commons JCS 2.1 RC1 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/ (r18146).
> 
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1235 .
> 
> The Subversion tag is:
> 
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.1
> (r1781745).
> 
> The release notes are at:
> 
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.1/RELEASE-NOTES.txt
> (r1781745).
> 
> The staged site is available as a tarball at
> 
> https://dist.apache.org/repos/dist/dev/commons/jcs/commons-jcs-site-2.1.tar.gz
> (r18146).
> 
> Please review the release candidate and vote.
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Bye, Thomas
> 
> 
> 
> -
> 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: [CONFIGURATION]: JavaDoc for generated classes (Was: [VOTE] Release Apache Commons Configuration 2.1.1 based on RC1)

[Oliver Heger]

Am 07.02.2017 um 08:35 schrieb Benedikt Ritter:
> 
>> Am 07.02.2017 um 08:29 schrieb Gary Gregory <garydgreg...@gmail.com>:
>>
>> Should we generate code in its own package?
> 
> Let’s move this to it’s own thread…
> 
> Generating the classes in their own packe would be an option. The package 
> could have a name that makes clear that the classes are generated. But I’d 
> leave that to Oliver since he knows the code base better then any of us.

This setup of the JavaCC-generated classes has been in place from the
very beginning. Just to suppress some Javadoc warnings during site build
does not seem a good enough reason for me to change it.

That said, if somebody is willing to do the change, I would not oppose.
But I would not be too surprised if this caused some subtile problems,
e.g. with visibility of classes.

Oliver

> 
> Benedikt
> 
>>
>> Gary
>>
>> On Mon, Feb 6, 2017 at 11:23 PM, Benedikt Ritter <brit...@apache.org> wrote:
>>
>>>
>>>> Am 06.02.2017 um 18:07 schrieb Oliver Heger <
>>> oliver.he...@oliver-heger.de>:
>>>>
>>>>
>>>>
>>>> Am 06.02.2017 um 00:00 schrieb Gary Gregory:
>>>>> +1
>>>>>
>>>>> bin zip MD5, SHA1, ASC OK.
>>>>> src zip MD5, SHA1, ASC OK.
>>>>> src zip RAT check OK.
>>>>> src zip CLIRR check OK.
>>>>>
>>>>> Building with 'mvn clean test' OK.
>>>>>
>>>>> Building site with 'mvn site'
>>>>>
>>>>> Using:
>>>>>
>>>>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>>>>> 2015-11-10T08:41:47-08:00)
>>>>> Maven home: C:\Java\apache-maven-3.3.9\bin\..
>>>>> Java version: 1.8.0_112, vendor: Oracle Corporation
>>>>> Java home: C:\Program Files\Java\jdk1.8.0_112\jre
>>>>> Default locale: en_US, platform encoding: Cp1252
>>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
>>>>>
>>>>> Fails with the usualy SLF4J garbage:
>>>>>
>>>>> [INFO]
>>>>> 
>>> 
>>>>> [INFO] BUILD FAILURE
>>>>> [INFO]
>>>>> 
>>> 
>>>>> [INFO] Total time: 02:53 min
>>>>> [INFO] Finished at: 2017-02-05T14:53:44-08:00
>>>>> [INFO] Final Memory: 67M/693M
>>>>> [INFO]
>>>>> 
>>> 
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
>>>>> project commons-configuration2: failed to get report for
>>>>> org.codehaus.mojo:cobertura-maven-plugin: Failed to execute goal
>>>>> org.apache.maven.plugins:maven-checkstyle-plugin:2.15:check (default)
>>> on
>>>>> project commons-configuration2: Execution default of goal
>>>>> org.apache.maven.plugins:maven-checkstyle-plugin:2.15:check failed: An
>>> API
>>>>> incompatibility was encountered while executing
>>>>> org.apache.maven.plugins:maven-checkstyle-plugin:2.15:check:
>>>>> java.lang.NoSuchMethodError:
>>>>> org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/
>>> String;ILjava/lang/String;Ljava/lang/Throwable;)V
>>>>> [ERROR] -
>>>>> [ERROR] realm =
>>>>> plugin>org.apache.maven.plugins:maven-checkstyle-
>>> plugin:2.15--1851305005
>>>>> [ERROR] strategy =
>>>>> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
>>>>> [ERROR] urls[0] =
>>>>> file:/C:/Users/ggregory/.m2/repository/org/apache/maven/
>>> plugins/maven-checkstyle-plugin/2.15/maven-checkstyle-plugin-2.15.jar
>>>>> [ERROR] urls[1] =
>>>>> file:/C:/Users/ggregory/.m2/repository/org/slf4j/slf4j-
>>> jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
>>>>> [ERROR] urls[2] =
>>>>> file:/C:/Users/ggregory/.m2/repository/org/slf4j/jcl-over-
>>> slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
>>>>> [ERROR] urls[3] =
>>>>> file:/C:/Users/ggregory/.m2/repository/junit/junit/3.8.1/
>>> junit-3.8.1.jar
>>>>> [ERRO

Re: [VOTE] Release Apache Commons Configuration 2.1.1 based on RC1

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. Artifacts and site
look good.

+1

Many thanks!
Oliver

Am 05.02.2017 um 15:23 schrieb Benedikt Ritter:
> Hi,
> 
> we’ve fixed some bugs since the release of Commons Configuration 2.1 so I’d 
> like to call a vote to release Commons Configuration 2.1.1 based on RC1.
> 
> Commons Configuration 2.1.1 RC1 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/configuration (svn rev. 1814)
> 
> The tag is here:
>   
> https://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_1_RC1
>  
> 
>  (svn rev. 1781755)
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1236/org/apache/commons/commons-configuration2/2.1.1/
> 
> These are the Maven artifacts and their hashes
> 
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1.pom
>  
> 
> (SHA1: abe302b96439550e835325980d0d01613ab20c07)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1-sources.jar
>  
> 
> (SHA1: 8a83b0672d6d38dc4f339e1cd330a83965ba9bd0)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1-javadoc.jar.asc
>  
> 
> (SHA1: ad7d67a009ce4113544e90da623ccb9e6aca54de)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1.jar.asc
>  
> 
> (SHA1: 4cadcaa33bb0dfd489b0dc0050778c7cdfc4c9f8)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1-javadoc.jar
>  
> 
> (SHA1: 8bcba252ffb93779800ea1b2b1d7961e5c46b562)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1.jar
>  
> 
> (SHA1: d97d5b3f8b58c52730d47e1a63c8d3258f41ca6c)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1-sources.jar.asc
>  
> 
> (SHA1: b242f50c7256a6846538725bb30fbceff42fa250)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1.pom.asc
>  
> 
> (SHA1: 61b8c23a7563c28f1234555c62c99cc2768b34f8)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1-test-sources.jar
>  
> 
> (SHA1: c7e7b840f262aa8935979dbca3ded6c357a44b0b)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1-test-sources.jar.asc
>  
> 
> (SHA1: 38419d43e8de7ade7a37d89ee60fb678d41dfca8)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1-tests.jar.asc
>  
> 
> (SHA1: 952d9120033857e5ab00eb17ae857f344ad6d731)
> /org/apache/commons/commons-configuration2/2.1.1/commons-configuration2-2.1.1-tests.jar
>  
> 
> (SHA1: 9c529ca7502f94ad5a748451103106174af512b5)
> 
> I have tested this with JDK 7 & 8 using Maven 3.3.9.
> 
> Details of changes since 2.1 are in the release notes:
>   
> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
>   
> http://home.apache.org/~britter/commons/configuration/2_1_1_RC1/changes-report.html
> 
> Site:
> 

Re: [VOTE] Release Apache Commons Configuration 2.1.1 based on RC1

[Oliver Heger]

Am 06.02.2017 um 00:00 schrieb Gary Gregory:
> +1
> 
> bin zip MD5, SHA1, ASC OK.
> src zip MD5, SHA1, ASC OK.
> src zip RAT check OK.
> src zip CLIRR check OK.
> 
> Building with 'mvn clean test' OK.
> 
> Building site with 'mvn site'
> 
> Using:
> 
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T08:41:47-08:00)
> Maven home: C:\Java\apache-maven-3.3.9\bin\..
> Java version: 1.8.0_112, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_112\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
> 
> Fails with the usualy SLF4J garbage:
> 
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 02:53 min
> [INFO] Finished at: 2017-02-05T14:53:44-08:00
> [INFO] Final Memory: 67M/693M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
> project commons-configuration2: failed to get report for
> org.codehaus.mojo:cobertura-maven-plugin: Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.15:check (default) on
> project commons-configuration2: Execution default of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.15:check failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-checkstyle-plugin:2.15:check:
> java.lang.NoSuchMethodError:
> org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
> [ERROR] -
> [ERROR] realm =
>  plugin>org.apache.maven.plugins:maven-checkstyle-plugin:2.15--1851305005
> [ERROR] strategy =
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/maven/plugins/maven-checkstyle-plugin/2.15/maven-checkstyle-plugin-2.15.jar
> [ERROR] urls[1] =
> file:/C:/Users/ggregory/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
> [ERROR] urls[2] =
> file:/C:/Users/ggregory/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
> [ERROR] urls[3] =
> file:/C:/Users/ggregory/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[4] =
> file:/C:/Users/ggregory/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
> [ERROR] urls[5] =
> file:/C:/Users/ggregory/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
> [ERROR] urls[6] =
> file:/C:/Users/ggregory/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
> [ERROR] urls[7] =
> file:/C:/Users/ggregory/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[8] =
> file:/C:/Users/ggregory/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[9] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
> [ERROR] urls[10] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.3/maven-reporting-impl-2.3.jar
> [ERROR] urls[11] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
> [ERROR] urls[12] =
> file:/C:/Users/ggregory/.m2/repository/com/google/code/findbugs/jsr305/2.0.1/jsr305-2.0.1.jar
> [ERROR] urls[13] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/maven/doxia/doxia-core/1.2/doxia-core-1.2.jar
> [ERROR] urls[14] =
> file:/C:/Users/ggregory/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar
> [ERROR] urls[15] =
> file:/C:/Users/ggregory/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar
> [ERROR] urls[16] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar
> [ERROR] urls[17] =
> file:/C:/Users/ggregory/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar
> [ERROR] urls[18] =
> file:/C:/Users/ggregory/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
> [ERROR] urls[19] =
> file:/C:/Users/ggregory/.m2/repository/commons-validator/commons-validator/1.3.1/commons-validator-1.3.1.jar
> [ERROR] urls[20] =
> file:/C:/Users/ggregory/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
> [ERROR] urls[21] =
> file:/C:/Users/ggregory/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
> [ERROR] urls[22] =
> file:/C:/Users/ggregory/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
> [ERROR] urls[23] =
> 

Re: [VOTE] Release Commons Text 1.0-beta-1 based on RC2

[Oliver Heger]

Hi,

build works with Java 1.7 and 1.8 on Windows 10. The site build failed
for me with Java 1.8 with the following error:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on
project commons-text: Error generating
maven-checkstyle-plugin:2.13:checkstyle: Failed during checkstyle
execution: Unable to find suppressions file at location:
C:\data\dev\projects\OpenSource\text\commons-text-1.0-beta-1-src/checkstyle-suppressions.xml:
Could not find resource
'C:\data\dev\projects\OpenSource\text\commons-text-1.0-beta-1-src/checkstyle-suppressions.xml'.


I guess, the referenced file is missing from the distribution.

Artifacts and site look good, it would be helpful to have some user's
guide - currently only Javadocs are available. Would it be possible to
copy something from [lang]? (This can be added later.)

For the release notes it seems a bit strange that the initial release
contains bugfixes and removed classes. This may be okay because of the
history of [text]. Maybe, the release notes should state where most of
the classes come from and thus give a justification for the listed
changes. There is a typo in the bottom: "-Apachje Commons Text team".

There are some Checkstyle and Findbugs errors which may be worth looking
after, but probably nothing critical.

Mainly because of the problems with the site build I am -0.

Oliver

Am 26.01.2017 um 12:29 schrieb Rob Tompkins:
> Hello all,
> 
> This is a [VOTE] for releasing Apache Commons Text 1.0-beta-1 (from RC2).
> 
> Tag name:
>commons-text-1.0-beta-1-RC2 (signature can be checked from git using 'git 
> tag -v')
> 
> Tag URL:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=61eb9d01d3be74f692f9f9be5a988bdcbc09f6ec
>  
> 
> 
> Commit ID the tag points at:
>61eb9d01d3be74f692f9f9be5a988bdcbc09f6ec
> 
> Site:
>http://home.apache.org/~chtompki/commons-text-1.0-beta-1-RC2 
> 
> 
> Distribution files (committed at revision 17998):
>https://dist.apache.org/repos/dist/dev/commons/text/ 
> 
> 
> Distribution files hashes (SHA1):
>commons-text-1.0-beta-1-bin.tar.gz
>(SHA: b6aed4897e831960f916942e06183dfb6403c353)
>commons-text-1.0-beta-1-bin.zip
>(SHA1: 620a43c8c8dfc7b3a3cc2a5bca74bdd34a04b427)
>commons-text-1.0-beta-1-src.tar.gz
>(SHA1: bff10c7b2d60a19eb59f6901bb9c3a7b15ec5dec)
>commons-text-1.0-beta-1-src.zip
>(SHA1: 67d31b46394e0de29d7c15940c622ff0eada1880)
> 
> These are the Maven artifacts and their hashes:
>commons-text-1.0-beta-1-javadoc.jar
>(SHA1: 7c6e55802e4212426420dd4a0c67d45a21ccb7be)
>commons-text-1.0-beta-1-sources.jar
>(SHA1: 2524aa9bf1abf8e66f06eec020f322d145822f67)
>commons-text-1.0-beta-1-test-sources.jar
>(SHA1: c70ec496b9a77cf1eb03c029a738878794d66f4a)
>commons-text-1.0-beta-1-tests.jar
>(SHA1: 31575513a2dd455449008448d8ad38251c44269f)
>commons-text-1.0-beta-1.jar
>(SHA1: fd7717aabcbccef124f5f694c009f7f76e028cd2)
>commons-text-1.0-beta-1.pom
>(SHA1: 3998e133a3912580053a71cb9dd55d618bf9d129)
> 
> KEYS file to check signatures:
>http://www.apache.org/dist/commons/KEYS 
> 
> 
> Maven artifacts:
>https://repository.apache.org/content/repositories/orgapachecommons-1233 
> 
> 
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
> 
> This vote will be open at least 72 hours, i.e. until 
> 2017-01-29T12:00:00Z
> (this is UTC time).
> 
> 
> Cheers,
> -Rob
> 
> [1] http://apache.org/foundation/voting.html 
> 
> 
> 

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

Re: [VOTE] Release Validator 1.6 based on RC1

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10, including the site
build with Java 1.8. Artifacts and site look good.

+1

Oliver

Am 16.02.2017 um 17:11 schrieb sebb:
> Time for another Validator release ...
> 
> ==
> 
> Validator 1.6 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/validator/1.6_RC1
> (revision 18365)
> 
> commons-validator-1.6-bin.tar.gz.sha1:e8ad0a47a5636e3b73882fdaffe743295335601d
> commons-validator-1.6-bin.zip.sha1:911731f57fe111236498544770f839f8171175ac
> commons-validator-1.6-src.tar.gz.sha1:8c9455ae1e766aa1cbd2d702f553fe5bc7339843
> commons-validator-1.6-src.zip.sha1:749f2fbfa3899e4255205d4d9a80552e752fa54b
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1238/commons-validator/commons-validator/1.6/
> 
> These are the artifacts and their hashes
> 
> /commons-validator/commons-validator/1.6/commons-validator-1.6-test-sources.jar
> (SHA1: b7a4f1c4c3a1d8a37eb61a1fc82f1aeb225c60ca)
> /commons-validator/commons-validator/1.6/commons-validator-1.6-javadoc.jar
> (SHA1: 48f9ff1edd4f5512a366a5b5024ad5a2f8136801)
> /commons-validator/commons-validator/1.6/commons-validator-1.6-tests.jar
> (SHA1: cdabf204bae01116651eb8a47ca8d24b53141fe3)
> /commons-validator/commons-validator/1.6/commons-validator-1.6-sources.jar
> (SHA1: a8767cdd63c800f00df9c2fc5604a8f7648fe832)
> /commons-validator/commons-validator/1.6/commons-validator-1.6.pom
> (SHA1: cbc0a98f640a70e4b92d0966104eb63b89105f01)
> /commons-validator/commons-validator/1.6/commons-validator-1.6.jar
> (SHA1: e989d1e87cdd60575df0765ed5bac65c905d7908)
> 
>  Details of changes since 1.5.0 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/validator/1.6_RC1/RELEASE-NOTES.txt
> http://home.apache.org/~sebb/validator-1.6-RC1/changes-report.html
> 
>   I have tested this with JDK 1.6, 1.7, 1.8 using Apache Maven 3.3.9
> 
>   The tag is here:
> 
> https://svn.apache.org/repos/asf/commons/proper/validator/tags/VALIDATOR_1_6_RC1/
> (revision 1783233)
>   N.B. the SVN revision is required because SVN tags are not immutable.
> 
>   Site:
> http://home.apache.org/~sebb/validator-1.6-RC1/
> 
>(some *relative* links are broken - these will be OK once the site
> is deployed)
> 
>   Clirr Report (compared to 1.5.1):
> http://home.apache.org/~sebb/validator-1.6-RC1/clirr-report.html
> 
>   RAT Report:
> http://home.apache.org/~sebb/validator-1.6-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 than 72 hours from now,
>   i.e. sometime after 16:30 GMT 19 Feb 2017
> 
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
> -
> 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] Commons-net 3.6 based on RC1

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. The site build
with Java 1.8 failed for me with a few Javadoc errors. Artifacts and
site look good.

+1
Oliver

Am 11.02.2017 um 17:55 schrieb sebb:
> It's about time to release the next version of NET.
> 
> ==
> 
> NET 3.6 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/net/
> (r18280)
> 
> commons-net-3.6-bin.tar.gz.sha1:4371f4e8a4d2fec11b4631d2fcde00138b18c167
> commons-net-3.6-bin.zip.sha1:86063352b8f7f8ac06ff30385b417126de2af787
> commons-net-3.6-src.tar.gz.sha1:94d57bd99fbdb3f4513434b01ee5f4ba034a0497
> commons-net-3.6-src.zip.sha1:b5e7c51b63c6cdf324a5c37c5369e7863040c6f4
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1237/commons-net/commons-net/3.6/
> 
> These are the artifacts and their hashes
> 
> /commons-net/commons-net/3.6/commons-net-3.6-test-sources.jar
> (SHA1: f683bc005e0767f257bfd9eae6ba0124defde123)
> /commons-net/commons-net/3.6/commons-net-3.6-sources.jar.asc
> (SHA1: c7d05f840d862008f6303f9ac684b0a1bac5e008)
> /commons-net/commons-net/3.6/commons-net-3.6-tests.jar
> (SHA1: 5d0261c00f6a4a82bae1f6c570e4de20401c8f7b)
> /commons-net/commons-net/3.6/commons-net-3.6.pom
> (SHA1: 9dd75a32c1edbde107486895f8f35258371227bb)
> /commons-net/commons-net/3.6/commons-net-3.6-examples.jar
> (SHA1: d66546454f7fcec996296bbe8d709851fddf0c81)
> /commons-net/commons-net/3.6/commons-net-3.6-javadoc.jar
> (SHA1: 93485df622081fe815417e06d5acfbb9e97a0636)
> /commons-net/commons-net/3.6/commons-net-3.6-sources.jar
> (SHA1: 961dc27eabbe71bf32478baffe0e1be915ce7689)
> /commons-net/commons-net/3.6/commons-net-3.6.jar
> (SHA1: b71de00508dcb078d2b24b5fa7e538636de9b3da)
> /commons-net/commons-net/3.6/commons-net-3.6-ftp.jar
> (SHA1: 7d6800824dfed812250c64d9a8c9d4f4ddd5299b)
> 
> Details of changes since 3.5 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/net/RELEASE-NOTES.txt
> http://home.apache.org/~sebb/net-3.6-RC1/changes-report.html
> 
>   I have tested this with JDK 1.6, 1.7, 1.8 using Apache Maven 3.3.9
> 
>   The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_6_RC1/
> (r1782607)
> 
>   Site:
> http://home.apache.org/~sebb/net-3.6-RC1/
>(some *relative* links are broken - these will be OK once the site
> is deployed)
> 
>   Clirr Report (compared to 3.5):
> http://home.apache.org/~sebb/net-3.6-RC1/clirr-report.html
> 
>   RAT Report:
> http://home.apache.org/~sebb/net-3.6-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 than 72 hours from now,
>   i.e. sometime after 17:00 GMT Feb 14 2016
> 
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
> -
> 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: [DISCUSS] Scala at Commons

[Oliver Heger]

As we already host some C-code in Commons, I see no reason to reject
Scala or other JVM languages.

I have done some experiments with Scala myself and am very impressed by
this language. I might even have a small library which could become a
component.

One question: Which build tool would we use? I used to have some trouble
with Maven and IDE integration (but this was some time ago); with sbt I
have better experience, but this tool is complex and I don't know how it
can be used for site generation.

Oliver

Am 12.02.2017 um 16:52 schrieb Benedikt Ritter:
> Hello,
> 
> Commons mission has always been to provide a home for common _Java_ 
> libraries. Since my personal and professional interests are slowly shifting 
> from Java towards Scala, I’m looking for ways to contribute to Open Source 
> with Scala. For this reason I’d like to discuss whether Commons could be a 
> home for common Scala libraries as well. For example I’m thinking about 
> wrapper libraries which add Scala sugar to the existing libraries. 
> Furthermore there are some Scala projects out there at the ASF (Kafka, Spark) 
> which my be interested in sharing code via Commons.
> 
> Regards,
> 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

[ANNOUNCEMENT] Commons Configuration 2.1 Released

[Oliver Heger]

The Apache Commons Team is pleased to announce the availability of
Apache Commons Configuration 2.1.

The Commons Configuration software library provides a generic
configuration interface which enables an application to read
configuration data from a variety of sources.

This is the first maintenance release for Apache Commons Configuration
2.x. It contains some bug fixes and also adds a few new features like a
better integration into Spring. A full list of all changes can be found
in the release notes at
  http://www.apache.org/dist/commons/configuration/RELEASE-NOTES.txt

Version 2.1 is fully source and binary compatible with the previous 2.0
version.

Source and binary distributions are available for download from the
Apache Commons download site:

http://commons.apache.org/proper/commons-configuration/download_configuration.cgi

Please verify signatures using the KEYS file available at the above
location when downloading the release.

For complete information on Commons Configuration, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Configuration website:

http://commons.apache.org/proper/commons-configuration/

Oliver Heger, on behalf of the Apache Commons community

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

[RESULT][VOTE] Release Configuration 2.1 based on RC3 (Update)

[Oliver Heger]

After receiving some more votes, the vote to release Configuration 2.1
based on RC3 is now successful with the following votes (binding votes
marked with a *):

Gary Gregory:  -1 *
Jörg Schaible: +1 *
Oliver Heger:  +1 *
Raviteja Lokineni: +1
Benedikt Ritter:   +1 *

Thanks for all reviews.

Oliver


Am 16.08.2016 um 21:40 schrieb Oliver Heger:
> The vote to release Configuration 2.1 based on RC3 failed with the
> following binding votes:
> 
> Gary Gregory: -1
> Jörg Schaible:    +1
> Oliver Heger: +1
> 
> Oliver
> 
> Am 11.08.2016 um 22:02 schrieb Oliver Heger:
>> Hi all,
>>
>> after the failed votes for RC1 and RC2 a new RC has been created. There
>> has been further tweaking of the checkstyle configuration to solve build
>> problems on Java 1.6.
>>
>> Configuration 2.1 RC3 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/configuration
>> (revision 14770)
>>
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1197/
>>
>> Details of changes since 2.0 are in the release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
>>
>> https://home.apache.org/~oheger/configuration-2.1-rc3/changes-report.html
>>
>> Here is the tag:
>>
>> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC3
>> (revision 1755836)
>>
>> Site:
>>https://home.apache.org/~oheger/configuration-2.1-rc3/
>> (note some links in the menu are not yet working)
>>
>> KEYS:
>>   http://www.apache.org/dist/commons/KEYS
>>
>> Please review the release candidate and vote.
>> This vote will close no sooner than 72 hours from now, i.e. after 2000
>> GMT 14-Aug-2016
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>> Thanks!
>> Oliver
>>
>>
>>
>> -
>> 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 additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE][RC1] Release Commons Rng 1.0

[Oliver Heger]

Build works fine with Java 1.6 and 1.8 on Windows 10. Artifacts and site
look good.

+1

Oliver

Am 11.09.2016 um 16:55 schrieb Gilles:
> Hi.
> 
> This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).
> 
> Tag name:
>   RNG_1_0_RC1 (signature can be checked from git using 'git tag -v')
> 
> Tag URL:
>  
> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=commit;h=f8d23082607b9f2c7be7f489eb09627722440ee5
> 
> 
> Commit ID the tag points at:
>   f8d23082607b9f2c7be7f489eb09627722440ee5
> 
> Site:
>   http://home.apache.org/~erans/commons-rng-1.0-RC1-site
> 
> Distribution files:
>   https://dist.apache.org/repos/dist/dev/commons/rng/
> 
> Distribution files hashes (SHA1):
>   a221e862c8ff970a9ca3e7fbd86c3200d1f8780a commons-rng-1.0-bin.tar.gz
>   689b2bfbdb1856d4f47851d75762aab42057805a commons-rng-1.0-bin.zip
>   40b7b1639eedf91b5fad5d38e6ebec01e659048f commons-rng-1.0-src.tar.gz
>   6296dbabde10169d6365bda99f2af6dcc191e515 commons-rng-1.0-src.zip
> 
> KEYS file to check signatures:
>   http://www.apache.org/dist/commons/KEYS
> 
> Maven artifacts:
>  
> https://repository.apache.org/content/repositories/orgapachecommons-1199/org/apache/commons/commons-rng/1.0/
> 
> 
> [ ] +1 Release it.
> [ ] +0 Go ahead; I don't care.
> [ ] -0 There are a few minor glitches: ...
> [ ] -1 No, do not release it because ...
> 
> This vote will close in 72 hours, at 2016-09-14T15:10:00Z (this is UTC
> time).
> --
> 
> Thanks,
> Gilles
> 
> 
> -
> 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

[lang] LANG-1275 in upcoming 3.5 release?

[Oliver Heger]

Hi,

for LANG-1275 which I have just created I already have a fix that I
could directly commit. Is it okay to do this or would this interfere
with the preparations for the 3.5 release?

Oliver

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

Re: [lang] LANG-1275 in upcoming 3.5 release?

[Oliver Heger]

Am 09.10.2016 um 17:50 schrieb Matt Sicker:
> You can do a git rebase on the release branch to get master back in, though
> if you've already run the version update stuff on it, I'm not completely
> sure how that works (though it should work out just fine).

I would also go for the rebase approach. In case it helps, I also
uploaded the patch to the Jira ticket.

Oliver

> 
> On 9 October 2016 at 06:37, Benedikt Ritter <brit...@apache.org> wrote:
> 
>> Hello Oliver,
>>
>> Oliver Heger <oliver.he...@oliver-heger.de> schrieb am Sa., 8. Okt. 2016
>> um
>> 16:50 Uhr:
>>
>>> Hi,
>>>
>>> for LANG-1275 which I have just created I already have a fix that I
>>> could directly commit. Is it okay to do this or would this interfere
>>> with the preparations for the 3.5 release?
>>>
>>
>> Sorry for the late reply. I'm currently not sure how to get this into the
>> release branch. Do I have to rebase the release branch onto master? Or do I
>> merge master to release?
>>
>> Regards,
>> Benedikt
>>
>>
>>>
>>> Oliver
>>>
>>> -
>>> 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][RC2] Release "Apache Commons RNG" version 1.0

[Oliver Heger]

Am 17.09.2016 um 18:13 schrieb Gary Gregory:
> Hi All,
> 
> Gilles: I can see you are frustrated by the late comments and opinions when
> the code has been sitting in the repo for all to see. I hope we can resolve
> all of this amicably.
> 
> All: We have only one shot at 1.0, this will set the tone for a 1.x line.
> If things change/mature/break enough then it becomes 2.0, but if it happens
> too soon, then it might give the impression that our process is not mature.
> 
> It seems we have a difference of opinion as to whether the current code is
> ready for 1.0.
> 
> Now that we have both sides engaged in this discussion, we can try to
> resolve these differences in email agreements or in code changes. Maybe the
> -1 party could create Jiras to address specific issues, or should all this
> happen on the ML?

Currently only Gilles responded to the proposals of Emmanuel. I would
also be interested in the PoV of the other developers.

Oliver

> 
> From my experience, when I or someone finds any problem with an RC I
> rolled, I sigh, cancel, and redo; but not before complaining to myself that
> if there where not 50 steps to do a release, it would be less of a pain.
> 
> Gary
> 
> On Sat, Sep 17, 2016 at 8:28 AM, Emmanuel Bourg  wrote:
> 
>> Le 17/09/2016 à 13:34, Gilles a écrit :
>>
>>> Your behaviour is in blatant contradiction with the Apache
>>> motto, and this project's chair mantra (RERO), which is
>>> truly ignored by the facts.
>>
>> RERO isn't the Apache motto (and I'm not opposed to a release, I'm
>> opposed to declaring the current code as final and well polished).
>>
>> Apache is actually focused on consensus and collaborative work, your
>> behavior goes against that.
>>
>>
>>> [1] Work with me towards modularity.
>>
>> No thanks, I'm not interested in working with someone not open to
>> others' views. If even formatting a table properly is an issue for you
>> there is little I can do.
>>
>> Emmanuel Bourg
>>
>>
>> -
>> 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: [RESULT][VOTE] Release Configuration 2.1 based on RC3

[Oliver Heger]

Am 16.08.2016 um 21:40 schrieb Oliver Heger:
> The vote to release Configuration 2.1 based on RC3 failed with the
> following binding votes:
> 
> Gary Gregory: -1
> Jörg Schaible:    +1
> Oliver Heger: +1

After closing the vote, two more votes have been cast:
- Raviteja Lokineni: +1 (non-binding)
- Benedikt Ritter:   +1

If Benedikt's vote was counted, the release vote would pass with three
binding +1 votes. However, as the voting thread has already been closed,
this is formally not correct; so I am not sure how to proceed.

I will wait for some more time. If anybody has concerns regarding the
validity of this vote, please raise them now. If there are no
objections, I will start with the release preparations - probably on
Saturday afternoon UTC.

Oliver

> 
> Oliver
> 
> Am 11.08.2016 um 22:02 schrieb Oliver Heger:
>> Hi all,
>>
>> after the failed votes for RC1 and RC2 a new RC has been created. There
>> has been further tweaking of the checkstyle configuration to solve build
>> problems on Java 1.6.
>>
>> Configuration 2.1 RC3 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/configuration
>> (revision 14770)
>>
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1197/
>>
>> Details of changes since 2.0 are in the release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
>>
>> https://home.apache.org/~oheger/configuration-2.1-rc3/changes-report.html
>>
>> Here is the tag:
>>
>> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC3
>> (revision 1755836)
>>
>> Site:
>>https://home.apache.org/~oheger/configuration-2.1-rc3/
>> (note some links in the menu are not yet working)
>>
>> KEYS:
>>   http://www.apache.org/dist/commons/KEYS
>>
>> Please review the release candidate and vote.
>> This vote will close no sooner than 72 hours from now, i.e. after 2000
>> GMT 14-Aug-2016
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>> Thanks!
>> Oliver
>>
>>
>>
>> -
>> 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 additional commands, e-mail: dev-h...@commons.apache.org

Re: [beanutils] Gradle build weirdness

[Oliver Heger]

Am 27.09.2016 um 18:47 schrieb Raviteja Lokineni:
> Does anyone have any fix for it or have experienced the same?

Did you get this resolved? I just replaced the dependency in a Maven
build, and the new version was picked up immediately. So I think the
deployment to Maven central and meta data are correct.

Oliver

> 
> On Tue, Sep 27, 2016 at 12:45 PM, Raviteja Lokineni <
> raviteja.lokin...@gmail.com> wrote:
> 
>> Hi all,
>>
>> I had been using beanutils 1.9.2 as a runtime dependency in a gradle
>> build. After the release of 1.9.3 version, I've upgraded the version in
>> build.gradle but gradle somehow still picks up the older jar, although
>> there is no reference of it.
>>
>> More information on a gradle forums (didn't want to repeat the same here):
>> https://discuss.gradle.org/t/project-dependency-
>> picks-up-a-lower-version/19747
>>
>> Thanks,
>> --
>> *Raviteja Lokineni* | Business Intelligence Developer
>> TD Ameritrade
>>
>> E: raviteja.lokin...@gmail.com
>>
>> [image: View Raviteja Lokineni's profile on LinkedIn]
>> 
>>
>>
> 
> 

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

Re: [VOTE] Release Apache Commons Lang 3.5 based on RC1

[Oliver Heger]

Hi,

the build works fine for me with Java 1.6 and 1.8 on Windows 10, even
the site build is successful with Java 1.8. The artifacts and the site
look good.

However, I found a problem with the binary distribution: It contains two
spurious jars versioned with 3.5-SNAPSHOT. I think this needs to be
fixed as it is confusing for users.

So -1

Sorry
Oliver

Am 02.10.2016 um 17:23 schrieb Benedikt Ritter:
> Hi,
> 
> a long time has passed since we released Apache Commons Lang 3.4. We fixed
> quite a few bugs and introduced some nice new features. For this reason,
> I'd like to call a vote for releasing Apache Commons Lang 3.5 based on RC1.
> 
> Commons Lang 3.5 RC1 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/lang/LANG_3_5_RC1 (svn
> revision 16325)
> 
> Tag name:
>LANG_3_5_RC1 (signature can be checked from git using 'git tag -v')
> 
> Tag URL:
> https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=commit;h=4b2ec07989753b8f5e97cf0fdaa6cdd866ac30f5
> 
> Commit ID the tag points at:
>4b2ec07989753b8f5e97cf0fdaa6cdd866ac30f5
> 
> Maven artifacts are here:
>   https://repository.apache.org/content/repositories/orgapachecommons-1204
> 
> These are the Maven artifacts and their hashes:
> 
> commons-lang3-3.5-javadoc.jar
> (SHA1: 9a5aff3c756701522cdd812a21d1947c54857491)
> commons-lang3-3.5-sources.jar
> (SHA1: 505b17dd8097ad6d5a536197b38786aafb04b41b)
> commons-lang3-3.5-test-sources.jar
> (SHA1: c56a478f2c46640239e7453a98e646b94e6198e2)
> commons-lang3-3.5-tests.jar
> (SHA1: aa4653a9342ac9f49d147699d13e3bc27488b00f)
> commons-lang3-3.5.jar
> (SHA1: cef2bb5803f0325d88263ae2566ef5a31b28fad7)
> commons-lang3-3.5.pom
> (SHA1: 08b969f02dfa03fa493fd6eba4cb9dcceea5aefd)
> 
> I've tested with JDK 1.6, 7, 8 and Java 9 EA using Maven 3.2.5.
> Note that there are some problems when building on Java 9. We're currently
> investigating this, see https://issues.apache.org/jira/browse/LANG-1265
> To build on Java 9 you need to explicitly set the local provide to JRE:
> 
>   mvn -Djava.locale.providers=JRE clean test
> 
> Details of changes since 3.4 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/lang/LANG_3_5_RC1/RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/lang/3_5_RC1/changes-report.html
> 
> Site:
>   http://home.apache.org/~britter/commons/lang/3_5_RC1
> 
> Clirr Report (compared to 3.4):
>   http://home.apache.org/~britter/commons/lang/3_5_RC1/clirr-report.html
> (sorry, I messed up the site build and had to add the Clirr report
> manually...)
> 
> Note that Clirr reports several errors due to additions in the interface
> org.apache.commons.lang3.time.DatePrinter
> These are considered okay, since the DatePrinter interface is not meant to
> be implemented by clients. This change is documented in the release notes.
> 
> RAT report:
>   http://home.apache.org/~britter/commons/lang/3_5_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 than 72 hours from now,
> i.e. sometime after 17:30 UTC+2 05-October 2016.
> 
> [ ] +1 Release these artifacts
> [ ] +0 Okay, but...
> [ ] -0 Okay, but really should fix...
> [ ] -1 I oppose this release because...
> 
> Thank you,
> Benedikt
> 

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

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

[Oliver Heger]

Am 26.10.2016 um 21:21 schrieb Thomas Vandahl:
> Am 25.10.2016 um 21:38 schrieb Oliver Heger <oliver.he...@oliver-heger.de>:
>> when building on Windows 10 with Java 1.6 I get the error below. The
>> build with Java 1.8 is successful.
>>
>> On the distributions, I found some problems:
>> - Both the source and the binary distribution deflate in the same
>> folder. Typically, different folders are used.
> They should not overwrite anything important, though. 
> 
>> - The binary distribution does not only contain the jars but also all
>> hashes and checksums. I don't think that they are required.
> Yes, this happens when the assembly plugin builds from modules. I found this 
> a good idea, actually. Don't you?
Well, not blocking, so no need to argue.

>>
>> Is a site available for review?
> The site is available as tar.gz in the dist area. 
>>
>> One question regarding the beta status of the release: Are the artifacts
>> going to be deployed to Maven central?
> Yes. 
> 
>> Then there should be a special
>> handling of breaking changes (special maven coordinates and package
>> names indicating beta status). Otherwise, it would be good if the
>> release notes contained a corresponding hint.
> Ok. What would be required? We didn't do anything like that when releasing 
> beta-1. 
It is policy in commons to prevent binary incompatible artifacts with
the same package names and maven coordinates because this leads to jar
hell. So every time a release with breaking changes is made, there
should be a major version bump, and maven coordinates and package names
must be changed.

So the question is, are there incompatible changes between JCS 1.x and
the beta versions and the upcoming 2.0 final?

Oliver

> 
>> [ERROR] Failed to execute goal
> 
> This looks like a dependency is compiled with 1.7. I'll look into it. 
> 
> Bye, Thomas 
> 
> -
> 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 JCS 2.0-beta-2 based on RC2

[Oliver Heger]

Hi,

sorry, I don't want to stand in the way of the release. It is just that
in the past we used to be very careful with artifacts deployed to Maven
central and their compatibility. When I did alpha and beta releases for
[configuration] 2.0 it was decided that these artifacts must not be
published to Maven central because incompatibilities between succeeding
alphas/betas or the final 2.0 version are likely.

If the JCS betas are going to Maven central, I therefore assumed that
some means were taken to deal with incompatibilities. Otherwise, if some
3rd party project has the (stupid) idea to depend on such a beta, we are
in jar hell.

Oliver

Am 05.11.2016 um 23:52 schrieb Gary Gregory:
> There is no need to maintain BC since 2.0 is not out. Changing package
> names and Maven coordinates must also happen hand in hand. Changing one
> means changing the other.
> 
> Gary
> 
> On Nov 5, 2016 1:37 PM, "Thomas Vandahl" <t...@apache.org> wrote:
> 
>> Hi Oliver,
>>
>> On 05.11.16 21:18, Oliver Heger wrote:
>>> It seems that there are many breaking changes between this release and
>>> beta1; for instance, the clirr report for the core component lists
>>> numerous errors. Is it not against Commons policy to publish
>>> incompatible artifacts with the same maven and package coordinates to
>>> Maven central?
>>
>> I thought that is why we call it "beta"? It basically boils down again
>> to the question what should be considered a public API (which btw hasn't
>> changed since beta-1).
>> I have no problem with changing the coordinates but I'm pretty sure that
>> the next iteration to 2.0 final will introduce more incompatibilities
>> and we may run out of coordinates...
>>
>> As I see it, we are still in the transition from 1.3
>> (org.apache.jcs:jcs) to 2.0 (org.apache.commons.jcs:commons-jcs-core)
>> but I'm ready to change whatever is necessary to get this out of the door.
>>
>> Bye, Thomas.
>>
>>
>> -
>> 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 JCS 2.0-beta-2 based on RC2

[Oliver Heger]

It seems that there are many breaking changes between this release and
beta1; for instance, the clirr report for the core component lists
numerous errors. Is it not against Commons policy to publish
incompatible artifacts with the same maven and package coordinates to
Maven central?

Oliver

Am 05.11.2016 um 20:50 schrieb Gary Gregory:
> Good to know, TY. Hopefully someone will take the time to review over the
> weekend.
> 
> Gary
> 
> On Sat, Nov 5, 2016 at 12:37 PM, Thomas Vandahl  wrote:
> 
>> On 05.11.16 20:24, Gary Gregory wrote:
>>> Time to tally?
>>
>> I would like to. However, AFAIK, we are one PMC vote short.
>>
>> Bye, Thomas.
>>
>>
>>
>> -
>> 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 Weaver 1.3 based on RC2

[Oliver Heger]

Build worked for me with Java 1.6 and 1.8 on Windows 10. The site build
failed with Java 1.8, but was successful with 1.7 (following the build
instructions).

Artifacts and site look good.

+1

Minor nit: The OSGi meta data is problematic because all bundles have
the same symbolic name. But I guess, this is not relevant for the
intended use case.

Oliver

Am 13.10.2016 um 23:30 schrieb Matt Benson:
> I would like to release the [weaver] component.
> 
> Apache Commons Weaver 1.3 RC2 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/weaver/ (r16517).
> 
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1210 .
> 
> Tested with Oracle JDKs 6, 7 and 8; IBM JDKs 6 and 7.
> 
> The Subversion tag is:
>   http://svn.apache.org/repos/asf/commons/proper/weaver/tags/1.3_RC2
>  (r1764791).
> 
> Site (note some links may be broken; this will be fixed when the site
> is deployed):
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/index.html
> 
> RAT Report:
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/rat-report.html
> 
> Quality Reports (PMD/Checkstyle/Findbugs/japicmp):
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-processor/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-normalizer/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-antlib/project-reports.html
> 
> Note that compatibility (japicmp) reports have only been produced for
> artifacts that could conceivably be used programmatically by downstream
> users: namely, *not* weaver modules.
> 
> The only change from RC1 to RC2 has been the regeneration of the release
> notes.
> 
> Keys: https://dist.apache.org/repos/dist/release/commons/KEYS
> 
> Please review the release candidate and vote.
>   This vote will close no sooner than 72 hours from now, i.e. after
> 2130UTC 16-October 2016
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 

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

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

[Oliver Heger]

Hi,

when building on Windows 10 with Java 1.6 I get the error below. The
build with Java 1.8 is successful.

On the distributions, I found some problems:
- Both the source and the binary distribution deflate in the same
folder. Typically, different folders are used.
- The binary distribution does not only contain the jars but also all
hashes and checksums. I don't think that they are required.

Is a site available for review?

One question regarding the beta status of the release: Are the artifacts
going to be deployed to Maven central? Then there should be a special
handling of breaking changes (special maven coordinates and package
names indicating beta status). Otherwise, it would be good if the
release notes contained a corresponding hint.

Oliver

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test
(default-test) on project commons-jcs-jcache-extras: Execution
default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: There
was an error in the forked process
[ERROR] java.lang.UnsupportedClassVersionError:
org/apache/catalina/startup/Tomcat : Unsupported major.minor version 51.0
[ERROR] at java.lang.ClassLoader.defineClass1(Native Method)
[ERROR] at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
[ERROR] at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
[ERROR] at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
[ERROR] at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
[ERROR] at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
[ERROR] at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
[ERROR] at java.security.AccessController.doPrivileged(Native Method)
[ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
[ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
[ERROR] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
[ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
[ERROR] at java.lang.Class.getDeclaredMethods0(Native Method)
[ERROR] at java.lang.Class.privateGetDeclaredMethods(Class.java:2436)
[ERROR] at java.lang.Class.getDeclaredMethods(Class.java:1793)
[ERROR] at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.checkforTestAnnotatedMethod(JUnit4TestChecker.java:91)
[ERROR] at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.lookForTestAnnotatedMethods(JUnit4TestChecker.java:80)
[ERROR] at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.isValidJUnit4Test(JUnit4TestChecker.java:72)
[ERROR] at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.accept(JUnit4TestChecker.java:52)
[ERROR] at
org.apache.maven.surefire.util.DefaultScanResult.applyFilter(DefaultScanResult.java:98)
[ERROR] at
org.apache.maven.surefire.junit4.JUnit4Provider.scanClassPath(JUnit4Provider.java:311)
[ERROR] at
org.apache.maven.surefire.junit4.JUnit4Provider.setTestsToRun(JUnit4Provider.java:191)
[ERROR] at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:134)
[ERROR] at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
[ERROR] at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
[ERROR] at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :commons-jcs-jcache-extras


Am 21.10.2016 um 19:42 schrieb Thomas Vandahl:
> I would like to beta-release the [jcs] component.
> 
> Apache Commons JCS 2.0-beta-2 RC1 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/ (r16621).
> 
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1211 .
> 
> The Subversion tag is:
> 
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-beta-2
>  (r1766068).
> 
> The release notes are at:
> 
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-beta-2/RELEASE-NOTES.txt
> (r1766068).
> 
> Please review the release candidate and vote.
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Please be lenient with me as this is my first Commons release attempt.
> 
> Bye, Thomas
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

Re: [lang] LANG-1144: Multiple calls of org.apache.commons.lang3.concurrent.LazyInitializer.initialize() are possible

[Oliver Heger]

Am 23.10.2016 um 22:18 schrieb pascalschumac...@apache.org:
> Repository: commons-lang
> Updated Branches:
>   refs/heads/master 96c8ea2fb -> dc53e49b4
> 
> 
> LANG-1144: Multiple calls of 
> org.apache.commons.lang3.concurrent.LazyInitializer.initialize() are possible
> 
> minimal clean-up
> 
> 
> Project: http://git-wip-us.apache.org/repos/asf/commons-lang/repo
> Commit: http://git-wip-us.apache.org/repos/asf/commons-lang/commit/dc53e49b
> Tree: http://git-wip-us.apache.org/repos/asf/commons-lang/tree/dc53e49b
> Diff: http://git-wip-us.apache.org/repos/asf/commons-lang/diff/dc53e49b
> 
> Branch: refs/heads/master
> Commit: dc53e49b4afa5d59c533cf2b4918402c37411fbd
> Parents: 96c8ea2
> Author: pascalschumacher 
> Authored: Sun Oct 23 22:18:47 2016 +0200
> Committer: pascalschumacher 
> Committed: Sun Oct 23 22:18:47 2016 +0200
> 
> --
>  .../commons/lang3/concurrent/LazyInitializer.java  | 13 +++--
>  1 file changed, 7 insertions(+), 6 deletions(-)
> --
> 
> 
> http://git-wip-us.apache.org/repos/asf/commons-lang/blob/dc53e49b/src/main/java/org/apache/commons/lang3/concurrent/LazyInitializer.java
> --
> diff --git 
> a/src/main/java/org/apache/commons/lang3/concurrent/LazyInitializer.java 
> b/src/main/java/org/apache/commons/lang3/concurrent/LazyInitializer.java
> index a0f903c..ed84049 100644
> --- a/src/main/java/org/apache/commons/lang3/concurrent/LazyInitializer.java
> +++ b/src/main/java/org/apache/commons/lang3/concurrent/LazyInitializer.java
> @@ -78,11 +78,12 @@ package org.apache.commons.lang3.concurrent;
>   * @param  the type of the object managed by this initializer class
>   */
>  public abstract class LazyInitializer implements ConcurrentInitializer 
> {
> +
> +private static final Object noInit = new Object();
> +
> +@SuppressWarnings("unchecked")
>  /** Stores the managed object. */

Minor nit: As the field is now a constant, it should - according to the
Sun coding conventions - be named in uppercase: NO_INIT.

Oliver

> -
> -private static final Object NoInit = new Object();
> -
> -private volatile T object = (T) NoInit;
> +private volatile T object = (T) noInit;
>  
>  /**
>   * Returns the object wrapped by this instance. On first access the 
> object
> @@ -98,10 +99,10 @@ public abstract class LazyInitializer implements 
> ConcurrentInitializer {
>  // volatile field
>  T result = object;
>  
> -if (result == NoInit) {
> +if (result == noInit) {
>  synchronized (this) {
>  result = object;
> -if (result == NoInit) {
> +if (result == noInit) {
>  object = result = initialize();
>  }
>  }
> 

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

Re: [VOTE] Accept Commons RDF as a new component

[Oliver Heger]

+1

Oliver

Am 23.11.2016 um 14:47 schrieb Stian Soiland-Reyes:
> [Note: this is the Commons PMC vote on dev@commons - there's a
> concurrent IPMC VOTE thread on general@incubator]
> 
> Since Commons RDF entered incubation, it has evolved the understanding
> of its purpose, developed and released code base that is now
> stabilizing, moving towards a 1.0.0 release.
> 
> Although the Commons RDF developer community is small it has continued
> to grow interest, and Apache Commons feels like a natural home for the
> component; as intended when this podling was started. We appreciate
> all the help we have received from Commons while incubating, in
> particular Gary and Benedikt!
> 
> 
> The Commons RDF podling has voted to graduate from the Incubator
> to join Apache Commons as a new component:
> 
> https://lists.apache.org/thread.html/886ed903b3649203c794f7b7409f311b2391ebef1d9157177ba943b6@%3Cdev.commonsrdf.apache.org%3E
> 
> 
> This email carries over 3 Commons PMC binding votes from dev@commonsrdf:
> 
> 
> +1 Stian Soiland-Reyes (Commons PMC binding)
> +1 Benedikt Ritter (Commons PMC binding)
> +1 Gary Gregory (Commons PMC binding)
> 
> 
> Proposed component name: rdf
> 
> Proposed package name: org.apache.commons.rdf
> 
> Source code of RDF component:
> https://git-wip-us.apache.org/repos/asf?p=incubator-commonsrdf.git
> https://github.com/apache/incubator-commonsrdf
> 
> Incubator releases:
> http://archive.apache.org/dist/incubator/commonsrdf/
> 
> Website:
> http://commonsrdf.incubator.apache.org/
> 
> Project Maturity report (more links from there):
> https://github.com/apache/incubator-commonsrdf/blob/master/MATURITY.md
> 
> 
> This email propose a VOTE to accept Commons RDF as a new component of
> Apache Commons.
> 
> 
> Formally the Apache Incubator PMC will also need to agree the
> graduation, a concurrent vote thread is on
> 
> https://lists.apache.org/list.html?gene...@incubator.apache.org
> 
> 
> 
> 
> Please VOTE on graduating Commons RDF as new component:
> 
> [ ] +1 Yes, accept Commons RDF as new component
> [ ]  0 Undecided
> [ ] -1 No, because...
> 
> 
> This vote will be open for at least 72 hours, let's say 2016-11-26 17:00 UTC.
> 

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

Re: [VOTE] Release Apache Commons Lang 3.5 based on RC2

[Oliver Heger]

Build works fine for me with Java 1.6 and 1.8 on Windows 10. Site build
works with Java 1.8. Artifacts and site look good.

+1

Oliver

Am 13.10.2016 um 22:20 schrieb Benedikt Ritter:
> Hi,
> 
> finally I found the time to prepare Apache Commons Lang 3.5 RC2 :-)
> We could not release RC1, because I messed up the release archives. They
> contained some snapshot artifacts. This has been fixed in RC2. Furthermore
> LANG-1275 has been incorporated.
> 
> Lang 3.5 RC2 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/lang/LANG_3_5_RC2 (svn
> revision 16505)
> 
> Tag name:
>LANG_3_5_RC2 (signature can be checked from git using 'git tag -v')
> 
> Tag URL:
> 
> https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=commit;h=36f98d87b24c2f542b02abbf6ec1ee742f1b158b
> 
> Commit ID the tag points at:
>36f98d87b24c2f542b02abbf6ec1ee742f1b158b
> 
> Maven artifacts are here:
>   https://repository.apache.org/content/repositories/orgapachecommons-1209
> 
> These are the Maven artifacts and their hashes:
> 
> commons-lang3-3.5-javadoc.jar
> (SHA1: 337310e98410d577aca675930bb46405a0a8fb0c)
> commons-lang3-3.5-sources.jar
> (SHA1: f7d878153e86a1cdddf6b37850e00a9f8bff726f)
> commons-lang3-3.5-test-sources.jar
> (SHA1: dfb8a086a03cc9499cff808733fac667f5f50688)
> commons-lang3-3.5-tests.jar
> (SHA1: 8ca309192f104265c67a1570245ae827a8650af9)
> commons-lang3-3.5.jar
> (SHA1: 6c6c702c89bfff3cd9e80b04d668c5e190d588c6)
> commons-lang3-3.5.pom
> (SHA1: 08b969f02dfa03fa493fd6eba4cb9dcceea5aefd)
> 
> I've tested with JDK 1.6 using Maven 3.2.5 and Java 7, 8 and Java 9 EA
> using Maven 3.2.5.
> Note that there are some problems when building on Java 9. We're currently
> investigating this, see https://issues.apache.org/jira/browse/LANG-1265
> To build on Java 9 you need to explicitly set the local provide to JRE:
> 
>   mvn -Djava.locale.providers=JRE clean test
> 
> Details of changes since 3.4 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/lang/LANG_3_5_RC2/RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/lang/3_5_RC2/changes-report.html
> 
> Site:
>   http://home.apache.org/~britter/commons/lang/3_5_RC2
> 
> Clirr Report (compared to 3.4):
>   http://home.apache.org/~britter/commons/lang/3_5_RC2/clirr-report.html
> (sorry, I messed up the site build and had to add the Clirr report
> manually...)
> 
> Note that Clirr reports several errors due to additions in the interface
> org.apache.commons.lang3.time.DatePrinter
> These are considered okay, since the DatePrinter interface is not meant to
> be implemented by clients. This change is documented in the release notes.
> 
> RAT report:
>   http://home.apache.org/~britter/commons/lang/3_5_RC2/rat-report.html
> 
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now,
> i.e. sometime after 22:30 UTC+2 16-October 2016.
> 
> [ ] +1 Release these artifacts
> [ ] +0 Okay, but...
> [ ] -0 Okay, but really should fix...
> [ ] -1 I oppose this release because...
> 
> Thank you,
> Benedikt
> 

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

Re: [lang] Thread safety annotations

[Oliver Heger]

Am 28.11.2016 um 22:28 schrieb Gary Gregory:
> WRT licensing, I re-implemented the annotations in git master. Notice that
> all Javadocs are different and much simpler for now. Feel free to write
> more.

As the length of this thread shows, using annotations for the purpose of
documenting thread-safety can be a controversial topic.

I do not see the advantage over a plain text documentation in Javadoc.
Written text can even be more comprehensive.

The risk that the documentation goes out of sync with the implementation
is given in both scenarios. But if a class announced as thread-safe is
manipulated in a way that it is no longer thread-safe, I would consider
this as a bug. This is also a kind of backwards-incompatible change.

My 2 cents
Oliver

> 
> Gary
> 
> On Mon, Nov 28, 2016 at 12:55 PM, Gary Gregory 
> wrote:
> 
>> On Mon, Nov 28, 2016 at 12:18 PM, Matt Benson 
>> wrote:
>>
>>> I hoped to stay out of this. :) Points:
>>>
>>> * "provided" scope is another Maven mechanism that compiles against a
>>> given dependency but does not pull the dependency in as a runtime
>>> dependency. I personally prefer it to marking a dependency optional.
>>> * For annotations with only classfile retention, a future package
>>> rename e.g. lang4 would not require a consumer to upgrade just for the
>>> renamed annotation, though nothing would stop them from doing so. A
>>> given project could depend on either or both of lang3 and lang4 in any
>>> combination of compile-only or runtime-inclusive scope with no
>>> problems.
>>> * A standalone annotations component might be interesting, but I'm not
>>> sure if the proposed annotations constitute a critical mass adequate
>>> to justify it.
>>>
>>
>> I would have a hard time justifying a commons-lang3-annotations module
>> with only these 4 annotations.
>>
>> I could see having a Commons Annotations component though which for good
>> or bad would hold all annotations one could imagine having the Commons
>> world. Hm... it smells a bit though...
>>
>> Gary
>>
>>
>>>
>>> Matt
>>>
>>> On Mon, Nov 28, 2016 at 1:21 PM, Pascal Schumacher
>>>  wrote:
 Groovy had to change the license of its documentation from CC-A 3.0 to
>>> the
 Apache License during incubation:

 https://issues.apache.org/jira/browse/LEGAL-167
 http://markmail.org/message/2e7tehlwtpx625q4
 https://issues.apache.org/jira/browse/GROOVY-7470

 So I guess Commons is probably not allowed to use these files.


 Am 28.11.2016 um 18:58 schrieb Gary Gregory:
>
> On Mon, Nov 28, 2016 at 7:15 AM, Jochen Wiedmann
> 
> wrote:
>
>> On Mon, Nov 28, 2016 at 4:06 PM, sebb  wrote:
>>
>>> The code would not run without the JCIP jar.
>>
>> Are there licensing issues regarding that jar?
>>
> Hm, according to https://www.apache.org/legal/resolved.html, the
>>> license
> "Creative Commons Attribution (CC-A) 2.5" is discussed in the section
>>> "HOW
> SHOULD "WEAK COPYLEFT" LICENSES BE HANDLED?"
>
> It looks like we might have an issue but this is not clear to me as
>>> IANAL.
> I you look at the license summary
> https://creativecommons.org/licenses/by/2.5/ it sure seems OK, but our
> resolved.html has this license on a list of licenses to watch out for.
>
> So to be on the safe side, how do we best re-implement these? The
> annotation names we can keep as is but I would imagine that we'd want
>>> to
> re-write the Javadoc from scratch.
>
> Thoughts?
>
> Gary
>
>
>> Jochen
>>
>>
>> --
>> The next time you hear: "Don't reinvent the wheel!"
>>
>> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/
>> evolution-of-the-wheel-300x85.jpg
>>
>> -
>> 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 additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> 
>>
>> 
>> JUnit in Action, Second Edition
>> 

Re: [VOTE][RC6] Release Commons RNG 1.0

[Oliver Heger]

Build works with Java 1.6 and 1.8, site builds fine with 1.8. Artifacts
and site look good.

On the site I still miss an aggregated Javadocs Link.

+1
Oliver

Am 07.12.2016 um 00:22 schrieb Gilles:
> Hi.
> 
> This is a [VOTE] for releasing Apache Commons RNG 1.0 (from RC6).
> 
> 
> Tag name:
>   RNG_1_0_RC6 (signature can be checked from git using 'git tag -v')
> 
> Tag URL:
>  
> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=commit;h=4581a4520315657a4219b37c81f5db80e4a4e43c
> 
> 
> Commit ID the tag points at:
>   4581a4520315657a4219b37c81f5db80e4a4e43c
> 
> Site:
>   http://home.apache.org/~erans/commons-rng-1.0-RC6-site
> 
> Distribution files (committed at revision 17284):
>   https://dist.apache.org/repos/dist/dev/commons/rng/
> 
> Distribution files hashes (SHA1):
>   c5e70a523160ed848194eeba0efa2b14d23c7a61 commons-rng-1.0-bin.tar.gz.sha1
>   66d7701afc90aafa4c4b6e033b8df6cd84365161 commons-rng-1.0-bin.zip.sha1
>   ef56543c8882a0e4771de83ecf8b3be190f122cf commons-rng-1.0-src.tar.gz.sha1
>   3dc56b0793d8bbd703a4efa68547eb58f6fb5b35 commons-rng-1.0-src.zip.sha1
> 
> KEYS file to check signatures:
>   http://www.apache.org/dist/commons/KEYS
> 
> Maven artifacts:
>   https://repository.apache.org/content/repositories/orgapachecommons-1229/
> 
> Please select one of the following options[1]:
>  [ ] +1 Release it.
>  [ ] +0 Go ahead; I don't care.
>  [ ] -0 There are a few minor glitches: ...
>  [ ] -1 No, do not release it because ...
> 
> This vote will be open at least 72 hours, i.e. until 2016-12-10T00:00:00Z
> (this is UTC time).
> --
> 
> 
> Regards,
> Gilles
> 
> [1] http://apache.org/foundation/voting.html
> 
> 
> -
> 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][RC6] Release Commons RNG 1.0

[Oliver Heger]

Am 08.12.2016 um 12:24 schrieb sebb:
> Works OK for me, hashes and sigs
> 
> How did you download the files?
> 
> I have noticed that some browsers automatically unpack archives and
> it's not unknown for some to silently truncate the download.
> Check the file sizes.
Your theory seems to be correct. With Firefox (my version is 50.0.2),
zip files seem to be somehow manipulated. I tried with Chrome, and here
the signature checks are successful.

This must be a pretty new "feature" of Firefox; I always used it in the
past. Interestingly, the downloaded archives are not corrupt; they can
be opened with 7zip.

Sorry for the noise.
Oliver

> 
> 
> On 8 December 2016 at 07:58, Gilles <gil...@harfang.homelinux.org> wrote:
>> On Wed, 7 Dec 2016 21:39:02 +0100, Oliver Heger wrote:
>>>
>>> Hi,
>>>
>>> something seems to be wrong with the zip artifacts for both the source
>>> and the binary distributions. The checks for the signature and the md5
>>> sums fail for me.
>>
>>
>> What about the ".sha1" check?
>>
>> Gilles
>>
>>
>>> The tar.gz files are okay.
>>>
>>> Does anybody else have the same problems?
>>>
>>> Oliver
>>>
>>> Am 07.12.2016 um 00:22 schrieb Gilles:
>>>>
>>>> Hi.
>>>>
>>>> This is a [VOTE] for releasing Apache Commons RNG 1.0 (from RC6).
>>>>
>>>>
>>>> Tag name:
>>>>   RNG_1_0_RC6 (signature can be checked from git using 'git tag -v')
>>>>
>>>> Tag URL:
>>>>
>>>>
>>>>
>>>> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=commit;h=4581a4520315657a4219b37c81f5db80e4a4e43c
>>>>
>>>>
>>>> Commit ID the tag points at:
>>>>   4581a4520315657a4219b37c81f5db80e4a4e43c
>>>>
>>>> Site:
>>>>   http://home.apache.org/~erans/commons-rng-1.0-RC6-site
>>>>
>>>> Distribution files (committed at revision 17284):
>>>>   https://dist.apache.org/repos/dist/dev/commons/rng/
>>>>
>>>> Distribution files hashes (SHA1):
>>>>   c5e70a523160ed848194eeba0efa2b14d23c7a61
>>>> commons-rng-1.0-bin.tar.gz.sha1
>>>>   66d7701afc90aafa4c4b6e033b8df6cd84365161 commons-rng-1.0-bin.zip.sha1
>>>>   ef56543c8882a0e4771de83ecf8b3be190f122cf
>>>> commons-rng-1.0-src.tar.gz.sha1
>>>>   3dc56b0793d8bbd703a4efa68547eb58f6fb5b35 commons-rng-1.0-src.zip.sha1
>>>>
>>>> KEYS file to check signatures:
>>>>   http://www.apache.org/dist/commons/KEYS
>>>>
>>>> Maven artifacts:
>>>>
>>>> https://repository.apache.org/content/repositories/orgapachecommons-1229/
>>>>
>>>> Please select one of the following options[1]:
>>>>  [ ] +1 Release it.
>>>>  [ ] +0 Go ahead; I don't care.
>>>>  [ ] -0 There are a few minor glitches: ...
>>>>  [ ] -1 No, do not release it because ...
>>>>
>>>> This vote will be open at least 72 hours, i.e. until 2016-12-10T00:00:00Z
>>>> (this is UTC time).
>>>> --
>>>>
>>>>
>>>> Regards,
>>>> Gilles
>>>>
>>>> [1] http://apache.org/foundation/voting.html
>>>>
>>>>
>>
>>
>> -
>> 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 additional commands, e-mail: dev-h...@commons.apache.org