I had always assumed that the user home build.properties was the 'final
override'. I had also always assumed that the local build.properties
actually sat in CVS and contained the default values.
Craig, if I understand you correctly, you are saying the oppostie? I am
just trying to clear up my understanding of the process.
Thanks,
Scott Sanders
> > > -1 ... the load from ${user.home}/build.properties should go *last*,
> > > not *first*. You want to be able to set your "usual" properties in
your
> > > home directory, but override them for this particular package if
> > > necessary.
> >
> > lib.repo is defined in ~/build.properties
> >
> > It has to come before the project/build.properties because
> > project/build.properties references lib.repo
> >
> > If you have another way to do it, then you figure it out so that it
works
> > properly.
> >
> > -jon
> >
> >
>
> The philosophy used in all the non-Turbine implementations of build
> scripts :-) is that you *don't* define everything in the local project's
> build.properties -- you only code the exceptions. Therefore, you would
> define lib.repo in your project's file if you *didn't* want to use the
> standard one in your home directory.
>
> See my previous message for a real-life scenario where your proposed way
> creates an inability to do what *I* as a developer need to do.
>
> Craig
>
>
>
