[
https://jira.codehaus.org/browse/MNG-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339911#comment-339911
]
Jason van Zyl commented on MNG-5462:
------------------------------------
This is all handled by Aether and I honestly don't see anyone rewriting these
APIs. Aether handles dependency management just fine.
> Artifact resolution API doesn't take into account dependency management
> information from associated POM
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-5462
> URL: https://jira.codehaus.org/browse/MNG-5462
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0.5
> Reporter: Vincent Massol
>
> Example:
> {code}
> ArtifactResolutionRequest request = new ArtifactResolutionRequest()
> .setArtifact(this.project.getArtifact())
> .setArtifactDependencies(artifacts)
> .setCollectionFilter(filter)
> .setRemoteRepositories(this.remoteRepositories)
> .setLocalRepository(this.localRepository)
> .setManagedVersionMap(this.project.getManagedVersionMap())
> .setResolveRoot(false);
> ArtifactResolutionResult resolutionResult =
> this.repositorySystem.resolve(request);
> {code}
> In this case if some dependencies (found in "artifacts" variable) have
> dependencyManagement information, they won't be taken into account since the
> passed managed version map is the projet's one and thus won't contain this
> information.
> It seems really a burden on the API user to have to find the MavenProject for
> each artifact, get the managed version map for that artifact's POM and
> compute a global version map.
> I was really expecting the Maven Artifact resolution API to do the heavy
> lifting on that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
