ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24877] - exec task doesn't handle error conditions well
Date Fri, 21 Nov 2003 10:33:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24877>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24877

exec task doesn't handle error conditions well





------- Additional Comments From conor@cortexebusiness.com.au  2003-11-21 10:33 -------
I'm not sure it is better to leave this unset if there is no output. It is
possible but does it make sense? Should it apply to output properties as well.
What about people who output the properties after a run

<echo message="errors: ${erroroutput}"/>

The results for that would be the string ${erroroutput} if it is not set. Maybe
not that desirable.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message