You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/11/22 10:18:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17637143#comment-17637143 ]
Hudson commented on MDEP-674:
-----------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin » master #60
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/master/60/
> 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)