On Thu, 17 Jul 2003 08:20 pm, [EMAIL PROTECTED] wrote: > conor 2003/07/17 03:20:16 > > Modified: src/main/org/apache/tools/ant DemuxOutputStream.java > Project.java Task.java UnknownElement.java > src/main/org/apache/tools/ant/taskdefs Ant.java > CallTarget.java Java.java Redirector.java > src/main/org/apache/tools/ant/taskdefs/optional/junit > JUnitTask.java JUnitTestRunner.java > src/testcases/org/apache/tools/ant/taskdefs > DefaultExcludesTest.java DemuxOutputTask.java > Log: > Ensure all generated output gets through the output system to the > generating task >
This may have some flow on effects which I'll flag here. The Ant output handling now will pass every character through to the generating task without inserting line breaks at buffer full intervals. Also line breaks will not be converted to the platform line separator. So, if a java application running on Windows writes \n and not \r\n, the output stream that gets redirected to an ouput file will not have \n\r. It's not a big deal I think since the generating application should be in control - it may really want to generate a Unix format output. Since messages now typically contains the end-of-line characters, the log processing code will now strip line.separator chars from the end of a message since the output logger will println anyway. Long outputs from a <java> task that are not redirected will be long on the output log since the LogOutputStream will now accumulate the long line. This will only be apparent for lines > 1024 characters so not a major issue. Conor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]