commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <j...@socialchange.net.au>
Subject Re: [PATCH] beanutils build system
Date Mon, 25 Mar 2002 04:12:14 GMT
On Sun, Mar 24, 2002 at 06:06:50PM -0800, Jon Scott Stevens wrote:
> 
> If you let the ./build.properties have precedence over the
> ~/build.properties, then for example, if someone does a:
> 
> cp default.properties build.properties
> 
> Then they will have to go in and remove anything that is defined in their
> ./build.properties in order to get any effect. I see that as a bad thing.

Okay, let me see if I've got this right:

 - You have *all* project properties in default.properties
 - If you need to customize a jar property, you copy default.properties
   to build.properties, edit build.properties, and therefore the
   build.properties value overrides the default.properties value.
 - If the jar properties in default.properties work for you (as they
   most likely will with ${lib.repo}), then you don't have to do
   anything
 - Your ~/build.properties must be sourced first, or it's pretty
   useless.

Correct?

That may sound bleeding obvious, but I can tell you it's not obvious if
you've spent years with the other system. 

I certainly can't judge which system is better. If there were sensible
${lib.repo} defaults in build.xml, then you wouldn't have to copy
build.properties.sample, and the current system probably wouldn't annoy
you nearly as much.

> >> If anything you should do:
> >> 
> >> cp default.properties build.properties
> > 
> > Somewhere we need all the stuff currently in build.properties.sample. It
> > can live in default.properties if you like. Might be cleaner in
> > build.properties.sample.
> 
> Look at my diff more closely. ALL of the properties are in
> default.properties. Essentially, default.properties ==
> build.properties.sample. default.properties is just a better name and also
> prevents people from having to do a cp just to use the build system (which I
> find terribly annoying).

Ah yes.. I must have sounded dense.

> > There is no reason why the two systems can't
> > exist simultaneously. It just takes some compromise.
> 
> Sure...

I'm sure there's some technical compromise. Need to think some more. If
needs be, I'm personally happy to convert from override-by-exception to
turbine-style, now I understand it.


--Jeff

> 
> -jon
> 

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message