ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Headley, Bryan" <BHead...@universalaccess.net>
Subject RE: Is this a desirable feature?
Date Tue, 22 May 2001 16:28:35 GMT


> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@apache.org]
> Sent: Tuesday, May 22, 2001 1:42 AM
> To: ant-dev@jakarta.apache.org
> Subject: Re: Is this a desirable feature?
> 
> 
> Bryan Headley <BHeadley@universalaccess.net> wrote:
> 
> > So, we're looking at,
> >  
> > <property name="app.DEV.deployment.dir"
> >           value="/opt/deployment/forDev" />
> > <property name="app.QA.deployment.dir" 
> >           value="/opt/deployment/forQa" />
> >
> > <property name="app.deployment.dir"
> >           value="${app.${build.for}.deployment.dir}"/>
> 
> I know this is a very simplified case, but I still think
> 
> <property file="${build.for}.properties" />
> 
> would be easier to maintain, with the added benefit that one could
> load default values for all properties after this task, so you'd only
> have to define the properties that are really different from the
> defaults in your specialized properties file.
> 
That would work, but I want all my properties in a single file, so I can
ensure that they stay in sync together. Well, that's what I prefer, not to
be confused with what I may have to do :-)

> Given that we'll have an import/include mechanism in Ant2 you can
> extend this approach to patternsets, taskdefs and so on.
> 
> Stefan
> 

Mime
View raw message