because having
env.WHATEVER=something
in a properties file seems ugly to me - thats the only reason. Having a
cleaner more representative property name seems better.
Erik
----- Original Message -----
From: "Diane Holt" <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Thursday, March 28, 2002 8:42 PM
Subject: Re: Overriding properties
> --- Erik Hatcher <[EMAIL PROTECTED]> wrote:
> > <property environment="env"/>
> > <property name="my.desired.prop" value="${env.WHATEVER}"/>
> > <property file="default.properties"/>
> >
> > then define my.desired.prop in default.properties.
>
> I'm not sure why you'd need the "my.desired.prop" -- just set:
> <environment_prefix>.<ENV_VAR_NAME>=<default.value>
> directly in your default properties file (or in your build file, if you're
> not using an external props file).
>
> Diane
>
> =====
> ([EMAIL PROTECTED])
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Movies - coverage of the 74th Academy Awards�
> http://movies.yahoo.com/
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
