Jason Dillon wrote:
On Jul 3, 2006, at 4:54 PM, Alan D. Cabrera wrote:
I think it is still a good idea to have them all extend from a
parent pom... there is still stuff that would be good to centralize,
but the parent and the child do not need to exists within the same
tree and do not need to share the same version.
I see no reason for there to be a parent POM. What stuff needs to be
centralized? Can you explain what the phrase "the parent and the
child do not need to exists within the same tree and do not need to
share the same version" means?
There is a bunch of shared config... like maven-one-plugin, ci, jira,
deployment (ssh), plugin repositories, distro mgmgnt. About 80 lines
from the current pom.xml for specs is going to be the same across all
specs modules. Which minus spaces is about 1/3 of the pom.xml. Its
about 1/2 of the pom when the bulk dependencyManagement is removed
(since it won't be needed to resolve all specs in every module).
Ok, so if we update a spec, say javamail, the version of this shared
config stays the same? If that's the case, then I'm warming up to it.
Regards,
Alan
