You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2017/04/03 07:08:41 UTC

[jira] [Commented] (MINSTALL-114) Plugin shouldn't depend on maven-compat dependency

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

Karl Heinz Marbaise commented on MINSTALL-114:
----------------------------------------------

[~rfscholte] Currently only for test scope it is depending on maven-compat ? So does that mean this is solved ? Or did you had something different in mind?

> Plugin shouldn't depend on maven-compat dependency
> --------------------------------------------------
>
>                 Key: MINSTALL-114
>                 URL: https://issues.apache.org/jira/browse/MINSTALL-114
>             Project: Maven Install Plugin
>          Issue Type: Improvement
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>
> When moving the prerequisite to Maven 3.0, then there should be no reason to still depend on maven-compat.
> The different distributions of Aether (Sonatype and Eclipse) cause a little bit of trouble but that should be solved by introducing maven-artifact-transfer



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