maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Stolwijk <nick.stolw...@gmail.com>
Subject Re: Clarification on dependencyManagement
Date Fri, 01 May 2009 00:46:15 GMT
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 <grettke@acm.org> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message