> on 12/5/2000 10:46 AM, "Christopher Elkins" <[EMAIL PROTECTED]> wrote:
>
> > Jon,
> >
> > <snip>
> >> @@ -4,11 +4,6 @@
> >>
> >> <project name="Turbine" default="jar" basedir=".">
> >>
> >> - <!-- Give user a chance to override without editing this file
> >> - (and without typing -D each time it compiles it -->
> >> - <property file="${user.home}/.ant.properties" />
> >> - <property file=".ant.properties" />
> >> -
> > <snip>
> >
> > Because Ant (currently) doesn't allow you to override properties that have
> > already been set, moving this block where you did makes it impossible to
> > override the defaults without editing build-turbine.xml. Is there a specific
> > reason why you moved it?
> >
> > --
> > Christopher Elkins
>
> Yea, I moved it cause it looked like it wouldn't do anything given that the
> properties are being set on top of the ones in .ant.properties. How is this
> actually working?
>
> -jon
>
Ant takes a first-come first-served approach to setting property values. For
instance, the default value for "build.compiler" in turbine-build.xml is
"classic"; By setting something like "build.compiler=jikes" in .ant.properties,
you can override it.
After setting a property value once, Ant (currently) ignores any further
attempts to set it. (Yeah, I know I'm glossing over the implementation details.)
I say "currently" because one of the changes discussed for Ant 2.0 is making
properties more mutable.
--
Christopher Elkins
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
