commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
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 ./ have precedence over the
> ~/, then for example, if someone does a:
> cp
> Then they will have to go in and remove anything that is defined in their
> ./ 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
 - If you need to customize a jar property, you copy
   to, edit, and therefore the value overrides the value.
 - If the jar properties in work for you (as they
   most likely will with ${lib.repo}), then you don't have to do
 - Your ~/ must be sourced first, or it's pretty


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, and the current system probably wouldn't annoy
you nearly as much.

> >> If anything you should do:
> >> 
> >> cp
> > 
> > Somewhere we need all the stuff currently in It
> > can live in if you like. Might be cleaner in
> >
> Look at my diff more closely. ALL of the properties are in
> Essentially, ==
> 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.


> -jon

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message