So it would
> be nice
> if we could either pass a '-userpref' option to tell ANT to check for a
> .properties file
> in ${user.dir}, or by daisy-chaining the .properties files so that ANT
> could read one
> .properties files and see that it needs to go read another.
>
have a look at the batch f
Erik
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Monday, February 04, 2002 8:54 AM
Subject: Re: Thoughts about properties
>
>
> As for (1), it seems to me that using an entity reference include doesn't
"Erik Hatcher"
tions.com> cc:
Subjec
day, February 01, 2002 7:02 AM
Subject: Re: Thoughts about properties
> On Fri, 1 Feb 2002 20:59, Erik Hatcher wrote:
> > > 1) Add a '-properties ' to specify a properties file
> > > which in effect "globally" for a single ant run. Obvi
On Fri, 1 Feb 2002 20:59, Erik Hatcher wrote:
> > 1) Add a '-properties ' to specify a properties file
> > which in effect "globally" for a single ant run. Obviously
> > it's possible to obtain something close to this functionality
> > by inserting the tag at t
This is really a topic for ant-dev, but I'll reply here for now...
- Original Message -
From: <[EMAIL PROTECTED]>
> I would like to suggest two extensions to ant's use of .properties files
> (maybe ant can already do these things, but between reading the doc
> and experimenting I didn't s
I would like to suggest two extensions to ant's use of .properties files
(maybe ant can already do these things, but between reading the doc
and experimenting I didn't see how):
1) Add a '-properties ' to specify a properties file
which in effect "globally" for a single ant run.