I was envisioning something like this:
<osfamily property="os.family" />
<property file="${os.family}.properties"/>
Maybe I'm missing something from this conversation, but this is how I would
accomplish platform-specific settings personally.
Erik
----- Original Message -----
From: "Diane Holt" <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, May 21, 2002 7:10 PM
Subject: Re: dynamic properties
> --- Erik Hatcher <[EMAIL PROTECTED]> wrote:
> > Also, don't miss out on ant-contrib's <osfamily> task too! That'd do
> > away with the need for <condition>.
>
> I'm not seeing how that'd do away with needing a <condition> -- it'd be a
> different condition, since you'd be testing on what the property set by
> <osfamily> was equal to, but I don't see how it'd do away with needing one
> at all. Am I just missing it?
>
> Diane
>
> =====
> ([EMAIL PROTECTED])
>
>
>
> __________________________________________________
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
> http://launch.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]>
