ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dale Anson <>
Subject Re: Ant 2.0
Date Tue, 10 Feb 2004 22:08:33 GMT
I've also ran into this problem, which prompted the <assert> task that 
is now in ant-contrib as a solution. It works a lot like Java's assert 
in that it can be turned on or off either through a command line 
parameter or by a property. It is a task, so does require build file 
modification, but it is useful for making sure that a property is set or 
set to the right value at a particular spot in the build.


Stefan Bodewig wrote:

> On Sun, 08 Feb 2004, Steve Loughran <> wrote:
>>One thing that was voted on (positively, I recall), way  way back in
>>time, was for Ant2.0 to fail on undefined properties.
> Although I've never looked into it, can't you already have it with a
> custom PropertyHelper?  If you can ensure that your custom property
> helper is the last one that gets called - and that it never gets
> called for know properties - you should be there.
> Provide this property helper and maybe add a new command line switch
> as syntactic sugar, done.
>>3. But there would be a non-throwing expansion method for code that
>>explicitly wanted to not fail on missing strings in their .
> The PropertyHelper could deal with it.
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message