ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: <available> / <condition> breaking immutability
Date Mon, 26 Nov 2001 14:01:48 GMT
On Sun, 25 Nov 2001, Erik Hatcher <>

> why does <available> and <condition> (and <uptodate>, <tstamp>,
> some others) break non-user property immutability?  Is this
> inadvertent or intentional?

inadvertent AFAIK.

> I'm (mostly?) of the opinion that <available> and such tasks that
> set a property based on some condition should force the
> setting/unsetting of the specified non-user property.

I can follow you here - of course this would be breaking backwards
compatibilty (sigh), but I'd consider builds that relied on
<available> not doing what it is supposed to do broken.


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

View raw message