bodewig 2004/05/13 00:01:08
Modified:src/etc/testcases/taskdefs defaultexcludes.xml
src/testcases/org/apache/tools/ant/taskdefs
DefaultExcludesTest.java
Log:
test1 failed unless it was the first test to run.
CVS:
bodewig 2004/05/13 00:13:53
Modified:.Tag: ANT_16_BRANCH WHATSNEW
docs/manual/CoreTasks Tag: ANT_16_BRANCH jar.html
src/etc/testcases/filters Tag: ANT_16_BRANCH concat.xml
src/etc/testcases/taskdefs Tag: ANT_16_BRANCH
On Thu, 17 Jul 2003, Conor MacNeill [EMAIL PROTECTED]
wrote:
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.
The log processing code or just
On Thu, 17 Jul 2003 09:52 pm, Stefan Bodewig wrote:
On Thu, 17 Jul 2003, Conor MacNeill [EMAIL PROTECTED]
wrote:
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
On Thu, 17 Jul 2003, Conor MacNeill [EMAIL PROTECTED]
wrote:
As it stands the content going to the listeners is largely the same
as pre-change.
OK, so it has been wrong before and we must keep it to remain
backwards compatible.
Nothing we could do, I guess.
Stefan
Hi Conor,
I am +1 on your changes.
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
bodewig 2003/05/09 05:10:36
Modified:.WHATSNEW
docs/manual coretasklist.html dirtasks.html
src/main/org/apache/tools/ant DirectoryScanner.java
src/main/org/apache/tools/ant/taskdefs defaults.properties
Added:
