+1 
I would go for <dependencyManagement/> as well.

Regards
Lars



Am Donnerstag 18 September 2008 15:26:46 schrieb Guillaume Nodet:
> Currently, we're mostly using properties to define versions of our
> dependencies. For example,
> <properties>
>    <jaxb.api.version>2.1</jaxb.api.version>
> </properties>
>
> and later in a submodule:
>
>  <dependency>
>     <groupId>javax.xml.bind</groupId>
>     <artifactId>jaxb-api</artifactId>
>     <version>${jaxb.api.version}</version>
> </dependency>
>
> It seems that this way of handling dependencies does not work very well.
> If another dependency uses the same mechanism but with a different
> version, I've seen maven using the one from the dependency instead of
> the one specified in the root pom.
> I think we should change this mechanism and use the
> <dependencyManagement/> section of the pom instead.
>
> Thoughts ?

Reply via email to