That's great, thanks. That's what we really need, more examples. Some of the
current examples are too vague or for very advanced users.> Subject: AW: AW:
token filtering> Date: Wed, 12 Nov 2008 06:44:53 +0100> From: [EMAIL
PROTECTED]> To: user@ant.apache.org> > I added a new example in the manual>
http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/CoreTasks/property.html?revision=712948>
>
---8-<-------8-<-------8-<-------8-<-------8-<-------8-<-------8-<-------8-<---->
<property environment="env"/>> <property file="${user.name}.properties"/>>
<property file="${env.STAGE}.properties"/>> <property
file="build.properties"/>> > This buildfile uses the properties defined in
build.properties. Regarding to the environment variable STAGE some or all
values could be overwritten, e.g. having STAGE=test and a test.properties you
have special values for that (like another name for the test server). Finally
all these values could be overwritten by personal settings with a file per
user. >
---8-<-------8-<-------8-<-------8-<-------8-<-------8-<-------8-<-------8-<---->
> Do you think that clarifies that?> > > Jan> > > > >-----Ursprüngliche
Nachricht-----> >Von: Rez [mailto:[EMAIL PROTECTED] > >Gesendet: Dienstag, 11.
November 2008 21:57> >An: Ant> >Betreff: RE: AW: token filtering> >> >> >Great,
thanks for your help> Subject: AW: token filtering> > >Date: Tue, 11 Nov 2008
06:54:36 +0100> From: > >[EMAIL PROTECTED]> To: user@ant.apache.org> > >I use >
>couple of property files packaged into my war file > >destined > >for
different environment such as Development, QA, > >Staging, > >Production. I
currently keep different versions of > >each > >file for each environment
having values specific to each > > >>env and the 4 different build targets for
each env refer to > > >>their own matching property files. They're kinda
getting out > >> >of hand, having muliple copies of each file! I would like >
>to > >keep one version of the files with the changing > >environment > >values
replaced with tokens and during the > >compile based on a > >flag or value
being set, such as if flag > >equal to QA, > >@ip.address@ should be replaced
with > >qa.ip=ip.add.re.ss. How > >is this possile without resorting > >to
ant.contrib?> > <property name="flag" value="qa"/>> > ><property
file="${flag}.properties"/>> <property > >file="default.properties"/>> > >
default.properties contains > >ALL values.> qa.properties contains the values
which DIFFER > >from the default one.> stageB.properties similar.> flag would >
>be "qa" or "stageB" and load the specified file.> If flag is > >something else
where you havent any properties file, the> > >non-existing> file is just
ignored.> > > Jan> > >
>---------------------------------------------------------------> >------> To
unsubscribe, e-mail: > >[EMAIL PROTECTED]> For additional commands, > >e-mail:
[EMAIL PROTECTED]> >
>_________________________________________________________________> >See how
Windows® connects the people, information, and fun > >that are part of your
life> >http://clk.atdmt.com/MRT/go/119463819/direct/01/> >> >
---------------------------------------------------------------------> To
unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL
PROTECTED]>
_________________________________________________________________
Color coding for safety: Windows Live Hotmail alerts you to suspicious email.
http://windowslive.com/Explore/Hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_safety_112008
