We have many projects that need to use common version numbers.
What is best practice for doing this with Ant/Ivy? Do you just inherit a wad of properties from Ant that have the version numbers in them, or is there a more formal mechanism a la Maven?
As you've pointed out I think this is the problem which the new extends functionality has been designed to solve.
To be completely honest I'm not a fan of parent-child modules in Maven.... However, just like you sometimes I want to nail lots of my modules to a common version of Spring.
The solution I used was to have a set of properties defined in my shared ivysettings file. This keeps my ivy specific properties separate from my ANT build properties.
来源：https://stackoverflow.com/questions/7019618/how-does-one-consolidate-version-management-in-ivy-like-parent-pom-dependencym