Hi Stephan: nod of appreciation for AntUnit :-),
Is the code base quiet because there are no further changes required,
or is there an alternative that I should use instead?
Being able to dump the logs is very handy when debugging the
tests/build scripts :-)
If the LogCapturer was only intended to be used to assert against the
logs, the EOL shouldn't interfere with existing functionality (unless
the assert is checking for multi line log entries; which I suspect is
the exception to the rule).
Regards,
Chris Holman
http://uk.linkedin.com/in/chrisdholman/
Quoting Stefan Bodewig <bode...@apache.org>:
On 2014-04-29, <chris.hol...@awltux.com> wrote:
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.
It's been years since I last looked at the code :-)
The resource really only is a side effect of having LogCapturer around
and making asssertions on the log content - i.e. the newlines would only
ever be noise for the assertion itself. AFAIR I never really thought of
people printing the contents.
Stefan
---------------------------------------------------------------------
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
