---- you Daniel Rall <[EMAIL PROTECTED]> wrote ----
> Berin Loritsch <[EMAIL PROTECTED]> writes:
> >> > You are right. I just looked at Avalon's setup, and it only has
> >> > two entries:
> >> >
> >> > <property file=".ant.properties"/>
> >> > <property file="${user.home}/.ant.properties"/>
> >> >
> >> > That allows a .ant.properties file in the ${base.dir} to override
> >> > properties in build.xml as well.
> >>
> >> Isn't that the same as <property file="build.properties"/> ?
> >
> > Yep. Just needs a standard name for the file--personally, I like
> > "build.properties" better.
>
> I've been using build.properties for per-project overrides and
> personal overrides, but I would much prefer that the one in my homedir
> was a dot file.
Hmmm - I'd lean towards just including build.properties, and not
ant.properties. Let the Ant-installed shell scripts take care of any Ant
customization that the user wants. These are customizations that the user
wants applied to this particular project, not to the Ant tool itself.
Re: dot file in homedir - sure, whatever, as long as it works on Windows.
8-)
Re: build.properties name: we could factor the work out one more step like
we have in xml-xalan/test/build.xml:
<!-- First, read in the user's own default properties, if they exist
-->
<property name="local.properties" value="my.test.properties"/>
<property file="${local.properties}" />
<!-- Then, read in the default checked-in properties -->
<property file="test.properties" />
Then we can all just agree the default name is build.properties, and let
users mess with it as they want. (Heck, they could even put in a
path/filename so they can decide where it lives...)
- Shane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
