All this is explained by http://wiki.eclipse.org/M2E_plugin_execution_not_covered . Basically, this maven plugin is problematic in the context of creating eclipse.
The message comes from the eclipse default lifecycle mapping, which you can override. I basically copied a snippet from the default lifecycle display and removed <message>...</message> from the <ignore> element
I have m2e v1.4.0.20130601-0317 (I think the one that comes with eclipse 4.3 Kepler), and I had two options: "workspace life cycle display metadata file" or just plugin configuration in pom.xml ,
1. workspace life cycle display metadata
You simply create a <workspace>\.metadata\.plugins\org.eclipse.m2e.core\lifecycle-mapping-metadata.xml file with the following contents:
<?xml version="1.0" encoding="UTF-8"?> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-remote-resources-plugin</artifactId> <versionRange>[1.0,)</versionRange> <goals> <goal>process</goal> </goals> </pluginExecutionFilter> <action> <ignore> </ignore> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata>
Then you will go to "Settings" and in the Maven / Lifecycle Mappings click the "Update workspace life cycle display metadata" button. After that you should update your maven projects (Maven / Update Project ...)
2. pom.xml
Or you can do it directly in pom.xml, so other developers will also benefit from it:
<pluginManagement> <plugins> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-remote-resources-plugin</artifactId> <versionRange>[1.0,)</versionRange> <goals> <goal>process</goal> </goals> </pluginExecutionFilter> <action> <ignore> </ignore> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> </plugins> </pluginManagement>
source share