----- Original Message -----
From: "Drew Davidson" <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Thursday, March 28, 2002 2:25 PM
Subject: Re: How can I have Ant replace unset properties as just empty
string
> Diane Holt wrote:
>
> > Use Ant's property immutability to set any property that's not already
set
> > to some other value. IOW, set the property to whatever default value you
> > want, and if it hasn't been set by some other means by the time it hits
> > your default-setting <property> tag, it'll get your default value.
>
> Diane, what's the theory behind replacing ${foo} with ${foo} if the 'foo'
> property has not been set? In make as well as other tools that have
variable
> expansion you usually get blank for unset variables. Just wondering what
> rationale there is for this behaviour.
the only other behavior which makes sense would be to brutally break the
build with a 'not known' error.
But using undefined properties in echo is a common build pattern, which
would break if we turned it off
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
