You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2017/05/14 09:19:04 UTC

[jira] [Commented] (MNG-6229) Write out optionality in Core IT Plugins for collection and resolution

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

Michael Osipov commented on MNG-6229:
-------------------------------------

Due to this change, it turns out that Maven 3.0.5 incorrectly calculates optional transtiive dependencies. Starting with Maven 3.1.0-alpha-1 all is well. The MNG-947 will be marked as expected fail for < 3.1.0-alpha-1.

> Write out optionality in Core IT Plugins for collection and resolution
> ----------------------------------------------------------------------
>
>                 Key: MNG-6229
>                 URL: https://issues.apache.org/jira/browse/MNG-6229
>             Project: Maven
>          Issue Type: Improvement
>          Components: Integration Tests
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>
> Several upcoming issues require to test wether a dependency is optional or not. Neither {{maven-it-plugin-dependency-collection}} nor {{maven-it-plugin-dependency-resolution}} do this at the moment.
> Add this information as {{(optional)}} in IT plugins output to verify optionality.



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