@Steve, you're right. DependencyManagement can force dependency versions (be it transitive or not) and does not incur any direct dependencies. So I'd say it's quite different than <dependencies> :)
Cheers! On Mon, Dec 12, 2011 at 10:50 PM, Steve Ebersole <[email protected]> wrote: > Hmm, my understanding is that <dependencyManagement/> affects transitive > dependencies whereas <dependencies/> does not. > > > > On Mon 12 Dec 2011 03:27:23 PM CST, Robert Watkins wrote: >> >> On 13/12/2011, at 2:42 AM, Steve Ebersole wrote: >> >>> If I understand the request properly, "pinned versions" are accomplished >>> in Maven using <dependencyManagement/> as distinct from <dependencies/>... >> >> >> No, Maven dependencyManagement is a shortcut technique for working with >> multiple POMs. When the POMs are expanded, any <dependencies> with missing >> versions get their version specification from the <dependencyManagement> >> (normally supplied in a 'parent' POM). The primary use of >> <dependencyManagement> is to make sure that all dependencies within a >> project are consistent. >> >> You can see this expansion effect using 'mvn help:effective-pom' >> >> The semantics of the version specification are the same, wether they are >> in the <dependency> or <dependencyManagement> section. >> >> -- >> "Software is too expensive to build cheaply" >> Robert Watkins twitter: @twasink http://twasink.net/ [email protected] >> <mailto:[email protected]> >> > > -- > [email protected] > http://hibernate.org > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
