Solution to the problem of using M2E to convert a project into a MAVEN project after the Eclipse report plugin execution not covered by lifecycle Configuration:xxx plugin

As you can see from the official documentation http://wiki.eclipse.org/M2E_plugin_execution_not_covered, the best solution is to work with Project Configurator specifically for the plugin,
For example, the Aspectj-maven-plugin used in the project is dedicated to Configurator, and users can use eclipse to find and install it online.
However, some plugins do not correspond to Project Configurator, and we can only configure them manually to tell m2e how to handle the goal of these plugins during eclipse build. The following is a typical configuration: ignores the related goal that perform native2ascii and dependency plugins. You don't have to hand-write this configuration yourself, eclipse can build for you.

	<plugin> <groupId>org.eclipse.m2e</groupId> <artifactid>lifecycle-mapping</artifactid > <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginexec utions> <pluginExecution> <pluginExecutionFilter> <groupId> org.apache.mave
							N.plugins </groupId> <artifactId> Maven-dependency-plugin </artifactId> <versionRange> [2.1,) </versionRange> <goals> <goal> un
							Pack-dependencies </goal> </goals> </pluginExecutionFilter> <action> <ignore/> </action> </pluginExecution> <pluginExecution> <pluginexec
								utionfilter> <groupId> Org.codehaus.mojo </groupId> <artifactId>
		Native2ascii-maven-plugin					</artifactId> <versionRange> [1.0-alpha-1,) </versionRange> <goals&
								Gt
							<goal>native2ascii</goal> </goals> </pluginExecutionFilter> <action> <ignore/> </action> </pluginExecution> </pluginExecutions> </lifecyclemapp
 Ingmetadata> </configuration> </plugin>