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:04:02 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17029233#comment-17029233 ] 

Karl Heinz Marbaise commented on MDEP-674:
------------------------------------------

Can you please share project examples cause in general I would say it's bad idea to use dependency plugin for packaging there are other plugins like maven-assembly-plugin etc. better choice but it depends on the use case? 

> 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
>          Components: copy
>            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)