On Thu, Sep 18, 2008 at 7:26 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> 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 ?
IMO, use of the dependencyManagement element is the correct way to
achieve this.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Blog: http://bruceblog.org/
