You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Schulte (JIRA)" <ji...@apache.org> on 2017/03/25 22:59:41 UTC
[jira] [Commented] (MRESOLVER-8) ScopeDependencySelector
incorrectly de-selects direct dependencies.
[ https://issues.apache.org/jira/browse/MRESOLVER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942042#comment-15942042 ]
Christian Schulte commented on MRESOLVER-8:
-------------------------------------------
Issue is fixed in the master branch of [my private maven repository on github|https://github.com/ChristianSchulte/maven-resolver/tree/master]. When interested, you can cherry pick the commit to your own repository and create a pull request for the apache master branch with just this commit yourself from there.
> ScopeDependencySelector incorrectly de-selects direct dependencies.
> -------------------------------------------------------------------
>
> Key: MRESOLVER-8
> URL: https://issues.apache.org/jira/browse/MRESOLVER-8
> Project: Maven Resolver
> Issue Type: Bug
> Reporter: Christian Schulte
> Priority: Critical
> Fix For: Maven Artifact Resolver 1.2.0 pre-reset
>
>
> The {{ScopeDependencySelector}} decides if a node is a direct dependency or transitive dependency differently based on the request performed. For the {{CollectRequest.setRootArtifact(Artifact)}} case, the class is working correctly. For the {{CollectRequest.setRoot(Dependency)}} case, the class is de-selecting direct dependencies instead of transitive dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)