on 8/21/01 1:06 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote:
> The first definition of a property wins -- that is understood. Now, play
> the following scenario (real life for me right now):
>
> * In ${user.home}/build.properties, I've defined my "commons-foo.jar"
> to point at the released version of the foo package, because that is
> what I generally want to use in my builds.
>
> * In building this particular component, I need to use hot-off-the-presses
> CVS code because I use features added since the release, so I override
> "commons-foo.jar" in my component-local version.
>
> Using your ordering, my override does not take effect -- putting the "user
> local" import third lets me do it.
>
> Craig
Fine, but the lib.repo stuff breaks.
Come up with a common ground then...
You could just comment out the one in your ~/build.properties or not define
it at all since it is defined in the project/build.properties.
p.s. Version numbers in .jar files have got yet another +1 from me because
you can have multiple versions of the same .jar file in your lib.repo and
point to them as needed. Nice.
-jon
