----- Original Message ----- From: "Erik Hatcher" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Monday, November 26, 2001 7:56 PM Subject: Re: <available> / <condition> breaking immutability
> Yes! I knew this, but didn't think of it as a counter-argument to letting > <tstamp> be immutable to DSTAMP, TSTAMP, and TODAY. And actually, why > aren't these just set automatically at the start of the build without having > to manually specify <tstamp>?! :) - this would actually make life a bit > easier so you could specify other properties relying on a datestamp before > the first <target> declaration rather than having to have an 'init' target > do this for you. makes sense, if they had names like ant.build.today, ant.build.tstamp. but would they be inherited in <ant>? > Boy, I sure am making a lot of work for myself, huh?! Or stirring up > trouble. No more than anyone else. -Steve (*)hey, maybe, just maybe, we could make <tstamp> a sibling of target :-) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
