Does anyone know if this behavior is a bug or intentional?
Thanks,
John
John Norvell wrote:
I'm working on an xlst script to convert our xml build logs to html and
have run across this somewhat odd behavior.
The javac task seems to log compile errors using the "warn" lo
https://sourceforge.net/projects/antcontrib/ extension library has the
task that uses conditions. Would you be able to use that?
-J
Jacob Kjome wrote:
In a macrodef, if I check a condition and that condition is true, I'd like to
return early from the macrodef and not run any of the rest of
I'm working on an xlst script to convert our xml build logs to html and
have run across this somewhat odd behavior.
The javac task seems to log compile errors using the "warn" logging
priority level with echo.
An example of a compile error would be:
"blahblah.java:619: cannot resolve symbol"
