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 23:00:43 UTC

[jira] [Commented] (MRESOLVER-12) Addition of unit tests for the various DependencySelector implementations to test things are working as documented.

    [ https://issues.apache.org/jira/browse/MRESOLVER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942046#comment-15942046 ] 

Christian Schulte commented on MRESOLVER-12:
--------------------------------------------

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.

> Addition of unit tests for the various DependencySelector implementations to test things are working as documented.
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRESOLVER-12
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-12
>             Project: Maven Resolver
>          Issue Type: Task
>            Reporter: Christian Schulte
>            Priority: Minor
>             Fix For: Maven Artifact Resolver 1.2.0 pre-reset
>
>
> The {{DefaultDependencyCollector}} heavily relies on various components provided by an application. There should be unit tests for testing that at least the {{ScopeDependencySelector}} and {{OptionalDependencySelector}} selector are working as stated in the Javadoc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)