They would not have to rename files to make things work... all the
properties got embedded into build.xml, so therefore no external files are
needed with the default config.
To customize is when you'd copy build.properties.sample, or hand create your
own tweaking the properties you wanted to override.
I prefer this because it keeps all defauilt build info inside build.xml
rather than there being two files necessary.
Erik
----- Original Message -----
From: "Jon Scott Stevens" <[EMAIL PROTECTED]>
To: "Lucene Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, February 26, 2002 8:19 PM
Subject: Re: cvs commit: jakarta-lucene build.xml
> on 2/26/02 5:10 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > - Moved properties from build.properties in here. build.properties
should be
> > removed and replaced by build.properties.sample.
>
> -1.
>
> A better way to deal with this is to follow what Scarab and other projects
> do which is to do this:
>
> <!-- Give user a chance to override without editing this file
> (and without typing -D each time it compiles it -->
> <property file="${user.home}/lucene.build.properties" />
> <property file="${user.home}/build.properties" />
> <property file="${basedir}/build.properties" />
> <property file="${basedir}/default.properties" />
>
> First, rename build.properties to default.properties
>
> Next, a developer can create one or more of the following files:
>
> ~/build.properties
> ~/lucene.build.properties
> lucene/build.properties
>
> That way, developers don't need to rename files in order to make things
work
> and the 'default' properties don't clutter up the build.xml file.
>
> Thanks,
>
> -jon
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
