Thanks,
Good point on the rationale behind this functionality. Not sure what
reason there could be to have the log reported as a single line.
Though I can imagine existing scripts working round it by inserting
EOL characters at the end of an echo statement.
I've come across others that have trouble using this task to send the
logs to file.
I've created a bug to track the issue: 56470: AntUnits logcontent task
returns a one line log string
https://issues.apache.org/bugzilla/show_bug.cgi?id=56470
Regards,
Chris
Quoting Antoine Levy Lambert <anto...@gmx.de>:
Hello Chris,
I wonder whether the current behavior of the LogCapturer has a
rationale and whether a backward compatibility needs to be preserved
for this aspect.
To submit a patch, the best is to create a bugzilla issue on
http://issues.apache.org/bugzilla and to attach
the output of svn diff -u .
Regards,
Antoine
On Apr 28, 2014, at 4:05 PM, chris.hol...@awltux.com wrote:
Hi,
I realise the AntUnit project is pretty quiet, but I have a fix I'd
like to submit.
The LogCapturer currently concatenates all messages onto the same
line. Not very readable when you send the log to file.
I've added an EOL to each append in method:
LogCapturer.messageLogged(BuildEvent event)
How do I go about submitting this fix?
Regards,
Chris Holman
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
