I think the idea of <dependencyManagement> is to baseline common dependencies
and their versions.
If you want to use the version 1.7.0 in the quoted example you need to specify
<dependency>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils</artifactId>
</dependency>
in your child/extended poms. However, if you do specify a version in the child
pom, it should override the one specified in the parent pom under
<dependencyManagement>
Cheers,
Rahul
----- Original Message -----
From: "Christian Schulte" <[EMAIL PROTECTED]>
To: "Maven Users List" <[email protected]>
Sent: Saturday, January 07, 2006 5:20 AM
Subject: [m2] dependencyManagement question ?
Hi,
I have a question regarding the <dependencyManagement> section in the pom.xml
files. When I have several dependencies and there are conflicts in the
transitive dependencies (e.g. commons-beanutils-1.6.1 and
commons-beanutils-1.7.0) I thought I could specifiy the version to use in the
<dependencyManagement> section. Is that correct ? Say I put
<dependencyManagement>
<dependency>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils</artifactId>
<version>1.7.0</version>
</dependency>
</dependencyManagement>
in my pom. This does not lead to maven using only that version no matter what
version is specified in the referenced poms ?
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
