Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=34211&projectId=132
Build statistics:
State: Failed
Previous Build: No previous build.
Started at: Fri 18 Jul 2014 05:55:55 +
Finished at: Fri 18 Jul 2014 05:56:04 +
Total time: 8s
Build Trigg
+1
Tested with Java 1.6 and 1.7 on Windows 8.1.
One minor nit: The checkstyle report appears twice in the menu under
"Project Reports".
Oliver
Am 16.07.2014 21:52, schrieb Benedikt Ritter:
> We have fixed quite a few bugs and added some significant enhancements
> since DbUtils 1.5 was release
It is a great change! I would also love to see an Ivy XML fragment in addition
to Maven. Graddle?
Gary
Original message From: Benedikt Ritter
Date:07/17/2014 11:57 (GMT-05:00)
To: Commons Developers List
Subject: [SITE] Add automatic generation of maven coords to site
bu
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=34195&projectId=136
Build statistics:
State: Failed
Previous Build: No previous build.
Started at: Thu 17 Jul 2014 16:23:21 +
Finished at: Thu 17 Jul 2014 16:24:01 +
Total time: 40s
Build Trig
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=34192&projectId=286
Build statistics:
State: Failed
Previous Build: No previous build.
Started at: Thu 17 Jul 2014 16:18:10 +
Finished at: Thu 17 Jul 2014 16:22:15 +
Total time: 4m 4s
Build Tr
Java 6 for 1.0 is ok here. We can do java 7 for 1.1.
Gary
Original message From: Benedikt Ritter
Date:07/17/2014 11:05 (GMT-05:00)
To: Commons Developers List
Subject: Re: [VOTE] Release Commons CSV based on RC2
CSVParser implicitly implements AutoClosable because it impl
Hi all,
since we're releasing all our components to maven central, it makes sense
to automatically generate the maven coords into the download page. I've
patched the commons-build-plugin locally so that it can generate the coords
for us.
Before I commit my changes, I'd like to hear how others fee
This vote is canceled because the source level was changed to Java 7
without consensus.
Releasing with Java 7 source level would enable try-with-resource.
Currently it seems, that people would rather like to see a Java 6
compatible release (see [1]).
I'll create RC3 Saturday morning. If nobody ob
CSVParser implicitly implements AutoClosable because it implements Closable
which extends AutoClosable in Java 7.
I assumed we had consensus about switching to Java 7 to enable
try-with-resource when using CSVParser (this was my bad, sorry). As far as
I understand try-with-resource won't work when
The 1.7 target is not needed. By changing the 1.7 to 1.6, I was able to
build on Java 6 with:
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e;
2014-06-17T09:51:42-04:00)
Maven home: C:\Java\apache-maven-3.2.2
Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
Java home: C:\Program
Le 17/07/2014 10:54, Jörg Schaible a écrit :
> The claim of Emmanuel that CSV uses AutoCloseable is simply not true:
>
> $> find commons-csv-1.0-src -type f -exec grep AutoClose {} +
You are right, sorry about that I got confused by the Javadoc of CSVPrinter:
http://people.apache.org/~britter/
Hi Benedict,
Benedikt Ritter wrote:
> Hi all,
>
> We had quite a few findings during the vote on CVS 1.0 RC1. I've worked
> through all the issues and fixed most of them. Now I'd like to release CSV
> 1.0 based on RC2.
>
> Changes since RC1 are:
>
> - CSV now requires Java 7 and the Java requi
12 matches
Mail list logo
