[ http://jira.codehaus.org/browse/MNG-2172?page=comments#action_61775 ]
Kenney Westerhof commented on MNG-2172: --------------------------------------- Related sources: maven-project/.../DefaultMavenProjectBuilder.java, line 320: call to createManagedVersionMap. Proposal: move to MavenProject. Line 340: call to ArtifactResolver.resolveTransitively( ..., ..., managedVersionMap, ...); maven-core/.../DefaultPluginManager.java, line 608. Call to ArtifactResolver.resolveTransitively(.., ..., ...) (without the managedVersionMap). Proposal: add call to moved createManagedVersionMap function as a parameter. > <dependencyManagement><dependency><version>'s are not used when evaluating > <plugin><dependencies><dependency> > ------------------------------------------------------------------------------------------------------------- > > Key: MNG-2172 > URL: http://jira.codehaus.org/browse/MNG-2172 > Project: Maven 2 > Type: Bug > Components: Inheritence and Interpolation > Environment: 2.0.2-SNAPSHOT > Reporter: John Allen > > > 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
