[VOTE] Release Apache Commons CSV 1.4 RC2

Apache Commons CSV 1.4 RC2 is available for review here: https://svn.apache.org/repos/asf/commons/proper/csv/tags/csv-1.4-RC2 (revision 1745420) commons-csv-1.4-bin.tar.gz (SHA1: 620580a88953cbcf4528459e485054e7c27c0889) commons-csv-1.4-bin.zip (SHA1: b0060ed8397bfec39b397807f63e778618f324ce)

Re: [CSV] License Issues in Commons CSV (Was: [VOTE] Release Apache Commons CSV 1.4 RC1)

On Tue, May 24, 2016 at 4:13 PM, Gary Gregory wrote: > On Tue, May 24, 2016 at 3:29 PM, sebb wrote: > >> On 24 May 2016 at 23:14, Gary Gregory wrote: >> > Ok, so maybe I just exclude these files from the release and add some >>

Re: [CSV] License Issues in Commons CSV (Was: [VOTE] Release Apache Commons CSV 1.4 RC1)

On Tue, May 24, 2016 at 3:29 PM, sebb wrote: > On 24 May 2016 at 23:14, Gary Gregory wrote: > > Ok, so maybe I just exclude these files from the release and add some > > Assume calls in the tests. I can do that... > > As I wrote, the Unit test clearly

Re: [CSV] License Issues in Commons CSV (Was: [VOTE] Release Apache Commons CSV 1.4 RC1)

On Tue, May 24, 2016 at 3:29 PM, sebb wrote: > On 24 May 2016 at 23:14, Gary Gregory wrote: > > Ok, so maybe I just exclude these files from the release and add some > > Assume calls in the tests. I can do that... > > As I wrote, the Unit test clearly

Re: [VFS] Jackrabbit

Hi, I happend to meet this old thread while looking at VFS-180, and was tempted to ask a question here. :-) I took a look at the current Jackrabbit based test cases, but I'm not sure if JR is the only option now. Tomcat has a built-in WebDavServlet to expose DAV access (read/write/list) and it is

Re: svn commit: r1745314 - in /commons/proper/fileupload/tags: commons-fileupload-1.3.2/ commons-fileupload-1.3.2RC1/

On 24 May 2016 at 08:32, wrote: > Author: jochen > Date: Tue May 24 07:32:56 2016 > New Revision: 1745314 > > URL: http://svn.apache.org/viewvc?rev=1745314=rev > Log: (empty) What's this about? Why is a tag being renamed? > Added: >

Re: svn commit: r1745345 - /commons/proper/fileupload/trunk/pom.xml

On 24 May 2016 at 13:04, wrote: > Author: jochen > Date: Tue May 24 12:04:34 2016 > New Revision: 1745345 > > URL: http://svn.apache.org/viewvc?rev=1745345=rev > Log: > Make m2e happy. Would this be a suitable candidate for the parent pom? > Modified: >

Re: [CSV] License Issues in Commons CSV (Was: [VOTE] Release Apache Commons CSV 1.4 RC1)

On 24 May 2016 at 23:14, Gary Gregory wrote: > Ok, so maybe I just exclude these files from the release and add some > Assume calls in the tests. I can do that... As I wrote, the Unit test clearly contains data extracted from the FERC CSV files. So the entire class needs

Re: [ANNOUNCE] Apache Commons git repositories now writable for all ASF committers

On 24 May 2016 at 22:55, Gary Gregory wrote: > On Tue, May 24, 2016 at 2:51 PM, sebb wrote: > >> On 24 May 2016 at 21:36, Gary Gregory wrote: >> > The more this goes on the more I wish we'd switch all Commons components >> to >>

Re: [CSV] License Issues in Commons CSV (Was: [VOTE] Release Apache Commons CSV 1.4 RC1)

Ok, so maybe I just exclude these files from the release and add some Assume calls in the tests. I can do that... On May 24, 2016 3:04 PM, "sebb" wrote: > On 24 May 2016 at 22:53, Gary Gregory wrote: > > On Tue, May 24, 2016 at 2:46 PM, sebb

Re: [CSV] License Issues in Commons CSV (Was: [VOTE] Release Apache Commons CSV 1.4 RC1)

On 24 May 2016 at 22:53, Gary Gregory wrote: > On Tue, May 24, 2016 at 2:46 PM, sebb wrote: > >> On 24 May 2016 at 22:09, Gary Gregory wrote: >> > On Mon, May 23, 2016 at 1:47 PM, Gary Gregory >> > wrote:

Re: [ANNOUNCE] Apache Commons git repositories now writable for all ASF committers

On Tue, May 24, 2016 at 2:51 PM, sebb wrote: > On 24 May 2016 at 21:36, Gary Gregory wrote: > > The more this goes on the more I wish we'd switch all Commons components > to > > git lock stock and two smoking barrels. > > That would not affect GitHub,

Re: [CSV] License Issues in Commons CSV (Was: [VOTE] Release Apache Commons CSV 1.4 RC1)

On Tue, May 24, 2016 at 2:46 PM, sebb wrote: > On 24 May 2016 at 22:09, Gary Gregory wrote: > > On Mon, May 23, 2016 at 1:47 PM, Gary Gregory > > wrote: > > > >> I just added a little more "docs" in revision 1745267. Awaiting >

Re: [ANNOUNCE] Apache Commons git repositories now writable for all ASF committers

On 24 May 2016 at 21:36, Gary Gregory wrote: > The more this goes on the more I wish we'd switch all Commons components to > git lock stock and two smoking barrels. That would not affect GitHub, which will still be readonly. > Gary > On May 24, 2016 12:43 PM,

Re: [CSV] License Issues in Commons CSV (Was: [VOTE] Release Apache Commons CSV 1.4 RC1)

On 24 May 2016 at 22:09, Gary Gregory wrote: > On Mon, May 23, 2016 at 1:47 PM, Gary Gregory > wrote: > >> I just added a little more "docs" in revision 1745267. Awaiting feedback. >> The commit is a comment in the POM in the RAT excludes section.

Re: [CSV] License Issues in Commons CSV (Was: [VOTE] Release Apache Commons CSV 1.4 RC1)

On Mon, May 23, 2016 at 1:47 PM, Gary Gregory wrote: > I just added a little more "docs" in revision 1745267. Awaiting feedback. > Any thoughts? No need to start another RC until this is squared away. Gary > > Gary > > On Mon, May 23, 2016 at 10:49 AM, Gary Gregory

Re: [Vfs] to git (was: Apache Commons git repositories now writable for all ASF committers)

I think we have to do 1-by-1 with infra anyway but I'd prefer to do it all. My guess from recollections from previous email threads is that folks would rather do this 1-by-1. You could start a [POLL] thread. Gary On Tue, May 24, 2016 at 1:48 PM, wrote: > I would

[Vfs] to git (was: Apache Commons git repositories now writable for all ASF committers)

I would nominate VFS to move to git, the question is do we keep want to do that one by one? Gruss Bernd -- http://bernd.eckenfels.net -Original Message- From: Gary Gregory To: Commons Developers List Cc: annou...@apache.org, Commons

Re: [ANNOUNCE] Apache Commons git repositories now writable for all ASF committers

The more this goes on the more I wish we'd switch all Commons components to git lock stock and two smoking barrels. Gary On May 24, 2016 12:43 PM, wrote: > Hello Jochen, > > I think the announcement is refering to the Apache hosted Git (writeable) > repositories

Re: [ANNOUNCE] Apache Commons git repositories now writable for all ASF committers

Hello Jochen, I think the announcement is refering to the Apache hosted Git (writeable) repositories (https://git-wip-us.apache.org/) - not the apache organisation on github or the public git mirror (https://git.apache.org). Those are always read-only mirrors. (Note that most commons projects

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

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

Stian to PMC

Stian, You should add yourself as a PMC member here: https://svn.apache.org/repos/asf/commons/cms-site/trunk/pom.xml Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition

Re: [fileupload] Remove Ant, and Gump files

On 2016-05-24, Jochen Wiedmann wrote: > thanks very much. In Summary, I understand that I can remove those > files: build.xml, gump.xml, build_gump.xml? Yes, I think so. Stefan - To unsubscribe, e-mail:

Re: [fileupload] Remove Ant, and Gump files

Hi, Stefan, thanks very much. In Summary, I understand that I can remove those files: build.xml, gump.xml, build_gump.xml? Jochen On Tue, May 24, 2016 at 12:23 PM, Stefan Bodewig wrote: > On 2016-05-24, Jochen Wiedmann wrote: > >> On Mon, May 23, 2016 at 10:13 PM, Gary

Re: [ANNOUNCE] Apache Commons git repositories now writable for all ASF committers

On 2016-05-24, Jochen Wiedmann wrote: > Doesn't work for my Github User (jochenw): > $ git push > Username for 'https://github.com': > Password for 'https://joch...@github.com': > remote: Permission to apache/commons-fileupload.git denied to jochenw. > fatal: unable to access >

Re: [ANNOUNCE] Apache Commons git repositories now writable for all ASF committers

On Sat, May 21, 2016 at 5:13 PM, Benedikt Ritter wrote: > Hello, > > a while back, the Apache Commons project decided to grant write access to > all ASF committers [1]. While setting this up for our SVN repositories was > easy, we had some problems to grant the necessary karma

Re: [fileupload] Remove Ant, and Gump files

On 2016-05-24, Jochen Wiedmann wrote: > On Mon, May 23, 2016 at 10:13 PM, Gary Gregory wrote: >> TODO: Drop Ant build? Not a blocker. > Unsure. For example, I don't know, whether the Gump build depends on > the Ant build, or not. I'd be ready to remove build.xml,

[fileupload] Remove Ant, and Gump files (Was: Release Apache Commons FileUpload 1.3.2 based on RC1)

On Mon, May 23, 2016 at 10:13 PM, Gary Gregory wrote: > TODO: Add a test code coverage report. Not a blocker. I have created FILEUPLOAD-273. > TODO: Drop Ant build? Not a blocker. Unsure. For example, I don't know, whether the Gump build depends on the Ant build, or

Re: Creating a Jira Issue

On Tue, May 24, 2016 at 10:17 AM, Jan Matèrne (jhm) wrote: > As Apache Commons is an umbrella project, each of its subprojects could use > its own bugtracking system. Thats how it is. But it only means I ought to rephrase my question with regards to subprojects. But never

AW: Creating a Jira Issue

> Stupid Question: There are only a few stupid questions, and this is none. ;) > How does one create a commons issue in Jira nowadays? All that I can > find is to create an infra issue (Create/Something Else, or > Create/Create Service Desk Request. As Apache Commons is an umbrella project,

Re: Creating a Jira Issue

Jochen Wiedmann schrieb am Di., 24. Mai 2016 um 09:54 Uhr: > Stupid Question: > > How does one create a commons issue in Jira nowadays? All that I can > find is to create an infra issue (Create/Something Else, or > Create/Create Service Desk Request. > Don't select

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

Thanks Stian and Benedikt! > Let's create a Jira issue to track the categorisation process. Do you mean to create a JIRA in LEGAL similar to LEGAL-250 to track this? Regards, Haifeng -Original Message- From: Benedikt Ritter [mailto:brit...@apache.org] Sent: Monday, May 23, 2016 3:36

Creating a Jira Issue

Stupid Question: How does one create a commons issue in Jira nowadays? All that I can find is to create an infra issue (Create/Something Else, or Create/Create Service Desk Request. Thanks, Jochen -- The next time you hear: "Don't reinvent the wheel!"

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

+1 Thanks for your work, Benedikt. On Mon, May 23, 2016 at 10:13 PM, Gary Gregory wrote: > +1 > > From src zip: MD5, SHA1, ASC OK. > Also src tar gz: MD5, SHA1, ASC OK. > > From src zip: mvn clean site OK. > > All reports OK except Checkstyle: > > I assume the

Re: [Rdf] Re: Nexus: Promotion Completed

Sergio Fernández schrieb am Di., 24. Mai 2016 um 09:21 Uhr: > Hi Bernd, > > On Tue, May 24, 2016 at 9:10 AM, wrote: > > > > It would be good if Incubator "releases" would be announced here on the > > development list. I havent been aware of all the

Re: [Rdf] Re: Nexus: Promotion Completed

Hi Bernd, On Tue, May 24, 2016 at 9:10 AM, wrote: > > It would be good if Incubator "releases" would be announced here on the > development list. I havent been aware of all the (excellent) work going on > in the commons-rdf sub project until I saw this release. The

Fwd: [RESULT] [VOTE] Release Apache CommonsRDF 0.2.0-incubating based on RC3

-- Forwarded message -- From: Sergio Fernández Date: Tue, May 24, 2016 at 8:45 AM Subject: [RESULT] [VOTE] Release Apache CommonsRDF 0.2.0-incubating based on RC3 To: gene...@incubator.apache.org Hi, after being open for more than 72 hours, the vote for

[Rdf] Re: Nexus: Promotion Completed

Hello, It would be good if Incubator "releases" would be announced here on the development list. I havent been aware of all the (excellent) work going on in the commons-rdf sub project until I saw this release. The Incubator site and the maven artifacts are all fully commons branded already,

Re: [VFS] Final steps for 2.1

Hello, I understand the dist module as preparing the artifacts for the binary and source distribution of the ASF download. And I agree that those target files must not be attached to the maven repository. As such the POM can be changed to a POM only module (or manually removed from the repo).