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

Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2015/04/22 00:05:59 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=14505886#comment-14505886 ] 

Robert Scholte commented on MINSTALL-114:
-----------------------------------------

http://svn.apache.org/repos/asf/maven/plugins/branches/m-install-p-3.0/ is a maven-compat runtime free version. I had to give it the test-scope due to the plugin-testing-harness.

> 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.4#6332)