> Please! Use standard ant "semantics" - first time you set a
> property you
> cannot change it again. Thus your loading sequence must be
> reversed! First ${user.home} then etc.
Sure you can! You can override property definitions in Ant...
The user should only have to specify the properties they want that are different from the standard build (if any).
For example:
Lets say I'm happy with all the standard libraries that hibernate provides, but I want to try a new library out. Say I download the latest snapshot of commons-lang.jar from the Jakarta website. Naturally, this snapshot will be more up to date than the one provided by Hibernate, since its newer. So, if it is the only file I want to compile Hibernate against that is different than the default jars, I could have a single entry in my ${user.home}/hibernate.build.properties file:
commons-lang.jar = /my/local/path/to/commons-lang.jar
Every other build dependency would use the standard libraries as specified in Hibernate's default build.properties file.
Isn't this desireable?
Les
