[VOTE] Release Apache Commons CSV 1.4 RC1

Apache Commons CSV 1.4 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/csv/1.4-RC1/ (revision 13733) commons-csv-1.4-bin.tar.gz (SHA1: 19806d3a6b2f8c6569f50b294da1d3f3a5be4429) commons-csv-1.4-bin.zip (SHA1: f551f471081c75a4cb6710b9981a3e0c858debd3) commons-csv-1.

RE: US Export classification & ECCN registration for encryption in commons?

>> Are you sure this is the case for commons-crypto? I thought we only >> supported JCE encryption and Open SSL encryption. From the definition of "OCI", I tend to not consider Commons Crypto is an Open cryptographic interface. The algorithm and key lengths it support are fixed. I would tend to

Re: [configuration] continuous integration

Am 22.05.2016 um 16:22 schrieb Benedikt Ritter: > Dennis Kieselhorst schrieb am So., 22. Mai 2016 um > 16:12 Uhr: > >> >>> Are you're talking about the Continuous Integration report of the web >> site >>> [1]? That is generated from the ciManagement section of pom.xml [2]. You >>> have to modif

Re: Re: [configuration] continuous integration

Dennis Kieselhorst schrieb am So., 22. Mai 2016 um 16:12 Uhr: > > > Are you're talking about the Continuous Integration report of the web > site > > [1]? That is generated from the ciManagement section of pom.xml [2]. You > > have to modify/add the section to configurations pom.xml and then > red

Re: [FILEUPLOAD] Release plans

Hi again, Benedikt Ritter schrieb am So., 22. Mai 2016 um 15:42 Uhr: > Hi, > > since trunk of FILEUPLOAD has breaking changes, I'm not going to create a > RC until we have resolved/come to an conclusion about this. The easiest way > to fix this is to readd java.io.Serializable to the classes whe

Re: Re: [configuration] continuous integration

> Are you're talking about the Continuous Integration report of the web site > [1]? That is generated from the ciManagement section of pom.xml [2]. You > have to modify/add the section to configurations pom.xml and then redeploy > the website using maven site-deploy [3]. Ok, I see it's defined in

[FILEUPLOAD] Release plans

Hi, since trunk of FILEUPLOAD has breaking changes, I'm not going to create a RC until we have resolved/come to an conclusion about this. The easiest way to fix this is to readd java.io.Serializable to the classes where it has been removed. I'm going work on a release of the stuff which is curren

Re: Proposed fluent string utils

Hello Micha, Micha Pringle schrieb am Fr., 20. Mai 2016 um 02:53 Uhr: > Gruß Benedikt, > Thank you for your reply during this busy time in the commons world. > I can explain the rationale. Adding a fully functional fluent string > library is a lot of work, requiring time I do not have a lot of.

Re: [configuration] continuous integration

Hello Dennis, Dennis Kieselhorst schrieb am So., 22. Mai 2016 um 13:19 Uhr: > > >>> > 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? > >>

Re: [configuration] continuous integration

>>> 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. A build is now configured here: https://builds.apache.org/jo

Re: [VFS] Final steps for 2.1

On 22 May 2016 at 03:54, Josh Elser wrote: > It's not a problem, it's an inconvenience. > > Ideally, Maven builds the artifacts with the intended names. This creates > consistency through every VOTE message, xsum/sig verification automation, > website links, and dist.a.o files. Does not follow, s