The default manager configuration in providers.xml registers the Tar
and Bzip2FileProvider conditionally based on commons compress classes.
For GzipFileProvider it uses unconditionally the java.util.zip package.
So I agre
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=30146&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Sat 3 May 2014 22:00:04 +
Finished at: Sat 3 May 2014 22:04:11 +
Total time: 4m 6s
Build Trigger: Schedul
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=30145&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Sat 3 May 2014 21:20:36 +
Finished at: Sat 3 May 2014 21:23:56 +
Total time: 3m 20s
Build Trigger: Schedu
On Sat, May 3, 2014 at 1:47 PM, Benedikt Ritter wrote:
> no, adding new methods doesn't break compatibility. If you're interested in
> this topic [1] is a very good read about it.
>
> [1] https://wiki.eclipse.org/Evolving_Java-based_APIs
>
Thanks for the evolving APIs link. I was actually aware o
just attached another patch on JCS-120 with makes jcs passing all TCKs
(CDI included).
Then we just need to:
1) fix the build on java 6 if broken
2) rework statistics
3) rework listeners
I would be ok if we get an alpha release without 2 and 3 but would be
a very great nice to have.
wdyt?
Rom
It does not usually unless the new methods are on interfaces and then it
depends on usage.
Gary
Original message From: Gabriel Reid
Date:05/03/2014 04:22 (GMT-05:00)
To: Commons Developers List
Subject: Re: [csv] Release planning for commons-csv
From what I've seen of th
Hi all,
we are working on [csv] for a long time now. The last two open issues that
we have targeted for 1.0 are CSV-35 [1] and CSV-58 [2]. Since we are
discussing how to fix this issues for over two years now, I think it
doesn't make sense to keep them blocking us from releasing 1.0 any longer.
Pe
Hello Gabriel,
no, adding new methods doesn't break compatibility. If you're interested in
this topic [1] is a very good read about it.
Regards,
Benedikt
[1] https://wiki.eclipse.org/Evolving_Java-based_APIs
2014-05-03 10:22 GMT+02:00 Gabriel Reid :
> From what I've seen of the discussion on
With 2.0 tar is supported out of the box, with 2.1 it is not. It depends
on commons-compress which is listed as an optional dependency.
Is this intentional? If so the documentation
(http://commons.apache.org/proper/commons-vfs/download.html) needs to be
updated prior to release.
--
Schalk W.
From what I've seen of the discussion on the two issues, the near-worst-case
scenario is the addition of a couple of new configuration methods, thus not
breaking backwards compatibility on the API. Does that count as API breakage?
> On 02 May 2014, at 20:48, Dan Tran wrote:
>
> API breakage w
Weird, it compiles on my box (Oracle1.7 and 1.8 on Mac) and I get another
compile error with Apple java-1.6.0_65
Have to finish a presentation till monday and work on BatchEE for $$dayjob. So
I will only be able to help again starting with Thuesday.
LieGrue,
strub
> On Friday, 2 May 2014,
11 matches
Mail list logo