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 [EMAIL PROTECTED] 2003-11-21 18:00 ------- Well, I like the OnError idea. Checking the return value works, but a) it's an ugly block of code needed after each and every exec and b) The ant documentation goes out of it's way to say that the definition of 'return code specifying failure' is OS-specific. This makes my code OS dependent, by making explicit that a non-zero return specifies failure. In answer to Steve, yes - the errorText property is an empty string but set. Finally, no one picked up on my first suggestion (perhaps not very clear). If you set failonerror="yes", the errror message returned should quote the error message returned by the sub-program, and return the error code - rather than just telling me the error code as it does now. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
