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

Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/10/28 11:29:00 UTC

[jira] [Updated] (MDEP-674) maven-dependency-plugin goals should define m2e metadata

     [ https://issues.apache.org/jira/browse/MDEP-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated MDEP-674:
---------------------------------
    Summary: maven-dependency-plugin goals should define m2e metadata  (was: maven-dependency-plugin:copy goal should define m2e metadata)

> maven-dependency-plugin goals 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
>            Assignee: Konrad Windszus
>            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.20.10#820010)