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 2020/02/03 20:03:02 UTC
[jira] [Moved] (MDEP-674) maven-dependency-plugin:copy goal should
define m2e metadata
[ https://issues.apache.org/jira/browse/MDEP-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Heinz Marbaise moved MNG-6849 to MDEP-674:
-----------------------------------------------
Component/s: (was: Dependencies)
Key: MDEP-674 (was: MNG-6849)
Project: Maven Dependency Plugin (was: Maven)
> maven-dependency-plugin:copy goal should define m2e metadata
> ------------------------------------------------------------
>
> Key: MDEP-674
> URL: https://issues.apache.org/jira/browse/MDEP-674
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Reporter: Mickael Istria
> Priority: Minor
>
> I often use the maven-dependency-plugon:copy goal for packaging purpose. However, Eclipse m2e complains that "plugin execution isn't covered...".
> This could be improved by adding just m2e lifecycle mapping metadata and leveraging the BuildContext API: https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)