ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Reilly <>
Subject Re: BuildException wrapping in <macrodef>
Date Wed, 20 Apr 2005 09:05:57 GMT
I had the attribute name "backtraceonerror", but I am sure
that a better name could be chosen.

Stefan Bodewig wrote:

><project xmlns:au="antlib:org.apache.ant.antlib.antunit">
>  <au:assertEquals expected="bar" actual="baz"/>
>I get
>/tmp/au.xml:2: The following error occurred while executing this line:
Expected 'bar' but was 'baz'
>what I really want is
>/tmp/au.xml:2:  Expected 'bar' but was 'baz'
>The reason for this is that assertEquals is a <macrodef> and
>MacroInstance unconditionally wraps any BuildExecption into a new one
>adding the macro definition's location.
>For tasks provided in antlibs, the user probably doesn't care whether
>it is a macrodef or a plain task.
>Would anybody object if I added an attribute to macrodef that you
>could use to turn off the wrapping (default would certainly be with
>Another side effect of this is that an ExitStatusException thrown by
><fail> nested into <macrodef> gets turned into a plain BuildException
Good point!


>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message