ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Reilly <>
Subject Re: Trapping RuntimeExceptions form Tasks
Date Tue, 11 May 2004 09:31:25 GMT
Stefan Bodewig wrote:

>On Wed, 05 May 2004, Peter Reilly <> wrote:
>>I see verify errors sometimes with beanshell and groovy
>Because you are reloading classes which is a problem in its own.  I
>think you'd better find a way to avoid these VerifyErrors instead of
>swallowing/ignoring them.  8-)
For the verify error, the problem was that groovy and beanshell were 
invalid bytecode - hence the verify error.
The notion is not to swallow / ignore them (unless the build script 
author wants to)
but to wrap them in a build exception to possibly provide some 
information as to
where the error happened - the line number of the build script from 
where the
error happened for example.

 From a build author, the seeing of an error is a problem wherer due to 
a file not
being present (using the "src" attribute) or a verify error in the byte 


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

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

View raw message