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=27007>. 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=27007 subant task fails even if failonerror="false" ------- Additional Comments From [EMAIL PROTECTED] 2004-02-17 22:50 ------- What Jose says makes an enormous ammount of sense and I like it, but it means either we are saying... "well don't write npe's" to the user or we would need to change the way tasks are called to auto-wrap them in a try catch that converts any exceptions into build exceptions. This could be a back compatability issue if people have custom tasks that call other tasks and rely on the non-build exceptions leaking out. Perhaps if the default inherited execute() looked like this: try { safeExecute() } catch (Exception e) { throw new BuildException(e) } Then existing tasks could obtain the new behavior by replacing execute() with safeExecute() and recompiling I think errors/generic throwables should not be caught. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
