maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <>
Subject [jira] Commented: (MNG-2172) <dependencyManagement><dependency><version>'s are not used when evaluating <plugin><dependencies><dependency>
Date Wed, 03 Nov 2010 18:16:03 GMT


Joerg Schaible commented on MNG-2172:

You silently imply that dependency management is only applied for the explicitly declared
dependencies of a plugin. Applying it for all dependencies of a plugin would be desastrous
and make very brittle builds, because an upgrade of a dependency of my project could break
a plugin used in teh lifecycle.

> <dependencyManagement><dependency><version>'s are not used when evaluating
> -------------------------------------------------------------------------------------------------------------
>                 Key: MNG-2172
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>         Environment: 2.0.2-SNAPSHOT
>            Reporter: John Allen
>            Assignee: Jason van Zyl
> dep management is not honoured for plugins dep evaluation.
> <kenney> hm.. looks like inheritance, after investigating.. the MavenMetaDataSource
doesn't use the MavenProject.getDependencyManagement
> <kenney> jah.. found it.
> <jallen> NICE, estimate... 30 mins or 30 hrs?
> <kenney> 30 mins
> <kenney> the maven-project DefaultMavenProjectBuilder uses a different method in
the ArtifactResolved to resolve deps than the maven-core DefaultPluginManager
> <kenney> but all the info is available..

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message