ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <>
Subject Re: To fail or not to fail
Date Fri, 30 Nov 2001 14:13:20 GMT
On Fri, 30 Nov 2001 23:52, Stefan Bodewig wrote:
> Hi,
> today I have committed two tasks that can cause build failures if
> certain conditions are met:
> * <input> makes the build fail, if the user ask for it
> * <waitfor> makes the build fail, if a given condition still doesn't
> pass after a given timeout.
> Some people may have been on this list when we discussed, whether
> <available> should be allowed to cause build failures.  That time, we
> said no, and I was one of the major proponents of "leave <fail> to
> <fail>".
> I still think that all build failures should be handled/caused by fail
> and would prefer if we removed the ability from the two above tasks.


> If adding if/unless attributes to <fail> 


> (or a nested <condition>
> element for the same task) 


> is the price for this, I am willing to pay it.
> Others?
> Stefan



PROGRAM: n.  a magic spell cast over a computer allowing it to turn
one's input into error messages.  v.t.  to engage in a pastime similar
to banging one's head against a wall, but with fewer opportunities for 

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

View raw message