> The other cool thing with a 'parent pom' is that you'd only specify > the dependency version once in the top level pom so that we would not > have to change it over and over again in the subprojects/modules.
I can't think of a single dependency that would apply to *all* projects. If it doesn't apply to all modules then you don't want it in the "root" POM do you? Otherwise it shows up in the dependency reports even though the dependency is not there ... We wouldn't put commons in the top level POM either would we? That isn't even created until later on down the line. Plus different modules would depend on different versions (since we are releasing independently now ..) > -bd- Sean
