Re: Log Flushing

2011-05-16 Thread Kevin Jackson
je suis tres occupe en ce moment a me chercher un nouveau job. Congratulations. Kev - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org

Re: Log Flushing

2011-04-29 Thread Antoine Levy Lambert
Merci Nicolas, je suis tres occupe en ce moment a me chercher un nouveau job. Antoine On 4/27/11 6:19 PM, Nicolas Lalevée wrote: Le 21 avr. 2011 à 23:26, Nicolas Lalevée a écrit : Le 21 avr. 2011 à 18:48, Antoine Levy-Lambert a écrit : I have dived in and committed the code attached to

Re: Log Flushing

2011-04-27 Thread Nicolas Lalevée
Le 21 avr. 2011 à 23:26, Nicolas Lalevée a écrit : Le 21 avr. 2011 à 18:48, Antoine Levy-Lambert a écrit : I have dived in and committed the code attached to 50507, and also made flush a no op in LineOrientedOutputStream. See my commits [1] and [2]. Something does not feel 100% right

Re: Log Flushing

2011-04-21 Thread Antoine Levy-Lambert
I have dived in and committed the code attached to 50507, and also made flush a no op in LineOrientedOutputStream. See my commits [1] and [2]. Something does not feel 100% right though. In the second commit I have tweaked unit tests to deal with some consequences of having made flush a no op. see

Re: Log Flushing

2011-04-19 Thread Nicolas Lalevée
Thank you very much for the pointers. The patch for the bug report #50507 seems to tackle the streaming issue. I guess that in Ant we always want to see the log by line, rather than with usual unix tools where the output is streamed. With unix tools, streaming is useful when pipelining

Re: Log Flushing

2011-04-19 Thread Antoine Levy-Lambert
On 4/19/2011 8:29 AM, Nicolas Lalevée wrote: Thank you very much for the pointers. The patch for the bug report #50507 seems to tackle the streaming issue. I guess that in Ant we always want to see the log by line, rather than with usual unix tools where the output is streamed. With unix

Re: Log Flushing

2011-04-19 Thread Nicolas Lalevée
Le 19 avr. 2011 à 16:42, Antoine Levy-Lambert a écrit : On 4/19/2011 8:29 AM, Nicolas Lalevée wrote: Thank you very much for the pointers. The patch for the bug report #50507 seems to tackle the streaming issue. I guess that in Ant we always want to see the log by line, rather than with

Re: Log Flushing

2011-04-19 Thread Conor MacNeill
One other possibility is to not bother doing anything in the LogOutputStream when flushed. Conor On Tue, Apr 19, 2011 at 06:03, Antoine Levy-Lambert anto...@gmx.de wrote: there is an interesting patch in this bug report : https://issues.apache.org/bugzilla/show_bug.cgi?id=50507 Regards,

Log Flushing

2011-04-18 Thread Conor MacNeill
Nicolas, The change you introduced to address this bug https://issues.apache.org/bugzilla/show_bug.cgi?id=50960 really breaks my output when running java processes because the autoflush is flushing at 128 byte boundaries. The log output stream always writes a line when flush is called. Here is

Re: Log Flushing

2011-04-18 Thread Nicolas Lalevée
Le 18 avr. 2011 à 08:10, Conor MacNeill a écrit : Nicolas, The change you introduced to address this bug https://issues.apache.org/bugzilla/show_bug.cgi?id=50960 really breaks my output when running java processes because the autoflush is flushing at 128 byte boundaries. The log

Re: Log Flushing

2011-04-18 Thread Antoine Levy-Lambert
there is an interesting patch in this bug report : https://issues.apache.org/bugzilla/show_bug.cgi?id=50507 Regards, Antoine On 4/18/2011 4:14 AM, Nicolas Lalevée wrote: Le 18 avr. 2011 à 08:10, Conor MacNeill a écrit : Nicolas, The change you introduced to address this bug

Re: Log Flushing

2011-04-18 Thread Antoine Levy-Lambert
In fact we have a number of open bugs concerning the handling of streams in exec and java : [1] Pipe Broken [2] Exec task may mix the stderr and stdout output while logging it [3] exec task sometimes inserts extraneous newlines [4] read on System.in hangs for forked java task Antoine [1]