maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <>
Subject Re: Transitive Dependencies for Unused Artifact
Date Mon, 19 Mar 2012 14:57:17 GMT
Typically each project module will have a parent that the individual 
developer does not play with.
It includes a dependency management section that specifies versions for 
all of the dependencies that the team cares about.

The individual module projects will list their dependencies but not 
specify a version number on each one since that is a team decision 
documented in the parent.


On 19/03/2012 10:26 AM, Lyons, Roy wrote:
> You can use dependencymanagement section to define the version as a filter to any subsequent
dependencies section.
> Putting it in dependencymanagement does not declare it as a dependency but does define
the version to be used when it find the dependency declared.
> Sent from my Blackberry.
> ----- Original Message -----
> From: kdobrik<>
> To:<>
> Sent: Mon Mar 19 09:06:03 2012
> Subject: Re: Transitive Dependencies for Unused Artifact
> Thank you for the answer.
> I will revisit my question. At the end of the day I need to centralize the
> versions used among all modules. Nevertheless these modules do not share all
> the jars needed. I need to refresh my Maven knowledge :)
> Once again thank you!
> --
> View this message in context:
> Sent from the Maven - Users mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Ron Wheeler
Artifact Software Inc
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

View raw message