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 16:17 ------- We do care when tests fail, but when you run 30k tests on each run, for different platforms, databases, configurations, you don't want to stop all of them I test #28 failed because someone forgot to catch a null. On the other hand, we do not only run junit tasks in the tests, we run custom tasks that prepare the test environment, and those were the ones who failed with a NPE, so using JUnit adaptors would not apply to this. Actually we have haltonerror and haltonfailure set to 'false' for junit. An I don't see your point in thinking that using subant like this is an abuse, it makes my ant build much clearer, instead of: <ant antfile="${boot.build.file}" target="-set0-daily"/> <ant antfile="${lib.build.file}" target="-set0-daily"/> <ant antfile="${compiler.build.file}" target="-set0-daily"/> <ant antfile="${xml.build.file}" target="-set0-daily"/> I have a clear: <subant target="-set0-daily" haltonerror="false" inheritall="true"> <dirset dir="${basedir}"> <include name="boot"/> <include name="lib"/> <include name="compiler"/> <include name="xml"/> </dirset> </subant> Please extend on the issue if you want. Having seen the code for SubAnt, in KeepGoing mode it handles the exception for each invocation, so it will continue even after a NPE inside a buildfile. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
