Yep - almost exactly what you describe is slated for Ant2 in some form or
another.
On Mon, 3 Sep 2001 15:39, JohnA wrote:
> I've set up a global properties file:
>
> <property file="/projects/ant.global.properties" />
>
> which contains some values for the compiler (e.g. build.compiler = jikes)
>
> I've tried to set up some of the other properties, "build.compiler.debug =
> on", but it doesn't seem to work. What I'd like to do is have minimal
> build.xml files by putting *all* the normal default values into a global
> properties file.
>
> I was wondering if ant can do this or if this idea was in the works for ant
> v2.0? (see below for a more detailed example)
>
> (please pardon this post, if it is a repeat!)
> John
> --------------------------------------
> For example, instead of writing this in a build.xml file:
>
> <javac
> srcdir="src"
> destdir="${build}"
> deprecation="on"
> debug="on"
> />
>
> I'd like to write these into the ant.global.properties file:
>
> javac.srcdir = src
> javac.deprecation = on
> javac.debug = on
> etc.
>
> Then, the build.xml file becomes:
>
> <javac destdir="${build}" />
>
> all other parameters supplied by the defaults in ant.global.properties
> files.
>
> If I need to I overwrite some properties in a build.xml:
>
> <javac srcdir="jsrc" destdir="${build}" />
>
> BTW taken to the "extreme" this would solve the compiler location
> problem... and, if the default properties file could, in turn, call an
> upper level properties file, then other benefits accrue.
--
Cheers,
Pete
---------------------------------------------------
"It is easy to dodge our responsibilities, but we
cannot dodge the consequences of dodging our
responsibilities." -Josiah Stamp
---------------------------------------------------
