On Sun, 25 Nov 2001, Erik Hatcher <[EMAIL PROTECTED]> wrote: > why does <available> and <condition> (and <uptodate>, <tstamp>, and > 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. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
