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
