This change was by design in 2.1. You should be overriding the version
in the child by specifying the dependencyManagement section again.
- Brett
On 08/04/2009, at 7:09 PM, Ben Storey wrote:
Hi,
We ran into a problem I thought I would make you aware of one of my
colleagues was running maven 2.1 and we were all running maven 2.0.9
When deploying with version 2.1.0 and you have properties setup like
the
following in the root project.
<prroperties>
<commons-logging.version>1.1</commons-logging.version>
</properties>
…
<dependencyManagement>
<dependencies>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>${commons-logging.version} </groupId>
</dependency>
</dependencies>
</dependencyManagement>
When you do the deploy with 2.0.9 it deploys like above, however when
deploying in 2.1. it substitutes the dependencyManagement version
property
like below.
<dependencyManagement>
<dependencies>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.1</groupId>
</dependency>
</dependencies>
</dependencyManagement>
This means in the child projects we cannot override the version by the
following:
<properties>
<commons-logging.version>1.1.1<commons-logging.version>
</properties>
Because maven does not do the substitution because there is no
variable to
substitute in the root descriptor.
With the way we are using maven currently the dependencyManagement
elements
we want to be able to override some of our own library versions.
Is this an enhancement or a bug?
Cheers
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
