Dominique Devienne wrote:
> empty. If foo is empty by mistake, how will one troubleshoot this?
and not a blank line. Undefined properties are echoed as literal
text, not skipped.
I'm well aware of that ;-) That's why I wrote "empty", not "not
defined". As in empty string vs null string.
The
--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
[SNIP]
> AFAIK, *any* task output is prefixed by the task's
> name. A line
> separator is output in my book ;-) I fail to see why
> it would be good
> to make an exception for somehow.
FWIW, I agree.
-Matt
>
> Go ahead and fix the "doc" bug if
> empty. If foo is empty by mistake, how will one troubleshoot this?
and not a blank line. Undefined properties are echoed as literal text, not
skipped.
I'm well aware of that ;-) That's why I wrote "empty", not "not
defined". As in empty string vs null string.
The proper way to output a line
Dominique Devienne wrote:
unless someone comes up with a good reason
why this is a bug rather than a feature.
It's a bug if it doesn't prefix that line with [echo] in non-emacs mode.
is not much different from ${foo} with foo being
empty. If foo is empty by mistake, how will one troubleshoot
unless someone comes up with a good reason
why this is a bug rather than a feature.
It's a bug if it doesn't prefix that line with [echo] in non-emacs mode.
is not much different from ${foo} with foo being
empty. If foo is empty by mistake, how will one troubleshoot this?
Sure, not a very good
Antoine Levy-Lambert wrote:
Hi Steve,
I think you are a committer too. Feel free to edit the documentation.
Regards,
Antoine
Steve Cohen wrote:
A very minor point:
The ant manual states that the echo task's message attribute is
required "unless data is included in a character section within
This appears to be false. I have by accident discovered that
has the effect of inserting a totally blank line into the output. It doesn't
Damn! That is exactly what I need! the maven ant-run plugin seems to
ignore the ${line.separator} property in an echo
Thanks for discovering this and +
Hi Steve,
I think you are a committer too. Feel free to edit the documentation.
Regards,
Antoine
Steve Cohen wrote:
> A very minor point:
>
> The ant manual states that the echo task's message attribute is
> required "unless data is included in a character section within this
> element."
>
> Th
