Stefan Bodewig wrote:
On Thu, 21 Apr 2005, Peter Reilly <[EMAIL PROTECTED]> wrote:
what I need is
+ } else {
+ throw ex;
+ }
This will cause the error to be reported from within the macro
definition. (i.e. from within the antlib resource).
True, so what I really need is
+ } else {
+ ex.setLocation(getLocation());
+ throw ex;
+ }
In short, I want to keep the original BuildException intact and hide
the macroedef location.
Ah, I see,
However now we have exceptions that are modified. I did this before
and DD explained that this is not a good thing to do.
In this case, it sounds like a good idea.
Peter
<fail> in your examples is supposed to throw an ExitStatusException
but the macro will turn it into a plain BuildException the way it is
right now. Same for assert* and the AssertionFailedException that
extends BuildException.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
