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=27219>. 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=27219 <fail> in an <imported> macro outputs wrong ------- Additional Comments From [EMAIL PROTECTED] 2004-02-25 17:09 ------- The backtrace is part of the macrodef for two purposes: 1) macrodefs can be difficult to get correct - esp, macrodefs calling macrodefs. 2) It is not obvious where to say the location of the error is- at the point of call, or within the macro For example: <macrodef name="f"> <sequential> <fail>the macro failed</fail> <!-- (1) --> </sequential> </macrodef> <f/> <!-- (2) --> Should the error location be (1) or (2) For a proper emulation of a real task, it should (2). I propose to add a attribute backtraceonerror (default true) to macrodef control the generation of the backtrace. 3: <macrodef name="f" backtraceonerror="no"> 4: <sequential> 5: <fail>A fail message</fail> 6: </sequential> 7: </macrodef> 8: <f/> Will only: BUILD FAILED /home/preilly/learning/ant/backtrace.xml:8: A fail message and 3: <macrodef name="f" backtraceonerror="yes"> 4: <sequential> 5: <fail>A fail message</fail> 6: </sequential> 7: </macrodef> 8: <f/> will generate: BUILD FAILED /home/preilly/learning/ant/backtrace.xml:8: Following error occured while executing this line /home/preilly/learning/ant/backtrace.xml:5: A fail message --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
