Hi,
the vote to release Apache Commoms Compress has finally started and even
if it should need one further re-roll (there has been a -1 and we'll see
whether this is enough to cancel the vote), the release should become
available in a week or two at most.
I intend to call for a vote on releasing
The EasyAnt project is pleased to announce its 0.8 version.
Easyant is a build system, that is based on Apache Ant and Apache Ivy.
Our goals are :
- to leverage popularity and flexibility of Ant.
- to integrate Apache Ivy, such that the build system combines a
ready-to-use dependency ma
On 08/09/2010 03:42 AM, Stefan Bodewig wrote:
I plan to add an disableTestListenerEvents
First I would like to hear an explanation of why printing a few lines to System.out causes such a big performance hit and why this cannot be fixed. What is waiting for
what to finish? Does the problem only
On 2010-08-10, Jesse Glick wrote:
> On 08/09/2010 03:42 AM, Stefan Bodewig wrote:
>> I plan to add an disableTestListenerEvents
> First I would like to hear an explanation of why printing a few lines
> to System.out causes such a big performance hit and why this cannot be
> fixed.
"such a big" i
Why does the StreamPumper poll like that? Surely it should just block
reading the InputStream?
To deal with InterruptedException, you can just do a timed read and test the
interrupted flag before looping back to the blocking read.
Danny.
On 10 August 2010 20:00, Stefan Bodewig wrote:
> On 201
On 2010-08-10, Danny Yates wrote:
> Why does the StreamPumper poll like that?
So it can be interrupted.
> Surely it should just block reading the InputStream?
It used to do just that.
On Windows if a process spawns children (grandchildren of Ant in this
case) they inherit the streams of their
Sorry, I didn't make myself clear. I was actually thinking of using a read
timeout so that the read call returns periodically and you can test
interrupted(), but on reflection, you can only do that with sockets.
I'll get my coat... ;-)
On 10 August 2010 20:45, Stefan Bodewig wrote:
> On 2010-0
On 2010-08-10, Danny Yates wrote:
> Sorry, I didn't make myself clear. I was actually thinking of using a read
> timeout so that the read call returns periodically and you can test
> interrupted(), but on reflection, you can only do that with sockets.
I think you will be able to do that with NIO2
