NO, ;) , not all dependencies in the parent should be dependencies of the child, that is completely up to the child project. For example, in the parent pom you have defined the depManagement for Hibernate, Spring-MVC and commons-validator. You have different child modules: project-web, project-model and project-data. Project-web should have a dependency on spring-mvc and commons-validator, project-data on hibernate and project-model on commons-validator. You set the version numbers in the parent pom and define the exact dependencies in the child poms.
Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, May 1, 2009 at 1:41 AM, Grant Rettke <[email protected]> wrote: > My understanding is YES, because if you were to enter them in the > dependencies section, they they would automatically be dependencies in > the child POM, too. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
