I don't have a binding vote but I have been caught out several times with
mis-matches in versions so +1 from me.
On Fri, Sep 19, 2008 at 8:48 AM, Freeman Fang <[EMAIL PROTECTED]>wrote:
> Of course +1 for using dependencyManagement.
>
> Avoid lots of error prone issue.
>
> Freeman
>
>
> Guillaume Nodet 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 ?
>>
>>
>>
>
>
