Skip to main content
Jump to: navigation, search

Difference between revisions of "M2E plugin execution not covered"

(New page: To solve some long-standing issues, m2e 0.13 requires explicit instructions what to do with all Maven plugins bound to "interesting" phases (see M2E interesting lifecycle phases) of pr...)
 
(Replaced content with "[https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html This page is now here]")
 
(42 intermediate revisions by 9 users not shown)
Line 1: Line 1:
To solve some long-standing issues, m2e 0.13 requires explicit instructions what to do with all Maven plugins bound to "interesting" phases (see [[M2E interesting lifecycle phases]]) of project build lifecycle. We call these instructions "project build lifecycle mapping" or simply "lifecycle mapping" because they define how m2e maps information from project pom.xml file to Eclipse workspace project configuration and behaviour during Eclipse workspace build.
+
[https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html This page is now here]
 
+
Project build lifecycle mapping configuration can be specified in project pom.xml, contributed by Eclipse plugins and there is also default configuration for some commonly used Maven plugins shipped with m2e. We call these "lifecycle mapping metadata sources". m2e will create error marker like below for all plugin executions that do not have lifecycle mapping in any of the mapping metadata sources.
+
 
+
Plugin execution not covered by lifecycle configuration:
+
org.apache.maven.plugins:maven-antrun-plugin:1.3:run
+
    (execution: generate-sources-input, phase: generate-sources)
+

Latest revision as of 07:13, 14 November 2014

This page is now here

Back to the top