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/11/22 10:10:00 UTC

[jira] [Resolved] (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 resolved MDEP-674.
----------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

Added notifications via the plexus-build-api about modified files/directories in https://github.com/apache/maven-dependency-plugin/commit/50a4b7017f1e66e92d8b66d0985ffdff05e93fcc.

> 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
>             Fix For: 3.4.0
>
>
> 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)