An error in Eclipse's tip in its pom file is as follows:
Plugin execution not covered by lifecycle Configuration:org.apache.maven.plugins:maven-compiler-plugin:3.1:compile ( Execution:default-compile, Phase:compile)
This means that M2E does not define the plug-in when it executes the MAVEN lifecycle management, so there is a hint of an error, in fact M2E provides an extension mechanism, and we can eliminate this error message by doing the following:
Scenario 1:
1. Enter the Window->preferences->maven configuration and enter the lifecycle mapping settings, such as:
As you can see, the file name for the M2E management maven lifecycle is lifecycle-mapping-metadata.xml, and the path to which it is stored
2. Next we will go to the corresponding path to modify the Lifecycle-mapping-metadata.xml file, but will find that the file in the location of the hint does not exist, then this time
Locate the file (for example) in the Org.eclipse.m2e.lifecyclemapping.defaults_xxxxxx.jar file under plugins in the installation directory of Eclipse:
By extracting the software, you can discover that the Lifecycle-mapping-metadata.xml file is indeed in the jar package, extracting it from the jar package and placing it in the path shown in the previous illustration.
(If you cannot find this jar, directly in the Browse ..., which is the root directory of your workspace.). metadata/.plugins/org.eclipse.m2e.core/ Lifecycle-mapping-metadata.xml
Create, save this file. )
3. Open the Lifecycle-mapping-metadata.xml file and add the unrecognized plugin to the file:
4. After the modification is complete, the "Update Maven projects on startup" option on the Window->preferences->maven will be ticked and the eclipse can be removed to eliminate the error.
Scenario 2
In Pom.xml in the plugin of the error in the outside of the package on a layer <pluginManagement></pluginManagement> as follows:
<pluginManagement><plugins>..........</plugins> </pluginManagement>
But this problem can not be solved at all, you need to refer again, or you can not use this plugin.
Scenario 3
Ignore out this plugin execution error under Windows->preferences->maven->error/warnings, such as:
Scenario 4
1. Open Eclipse or MyEclipse problem display window: ' Window ', ' Show View ', ' problems '
2. Right-click a display described as "' Plugin execution not covered by lifecycle Configuration:com.googlecode.mavenfilesync: Maven-filesync-plugin:1.0.0:generate (Execution:default, phase:initialize) ' "error message, in the pop-up menu selected" ' Quick Fix ' "
3. In the Quick Fix window, select ' permanently mark goal generate in Pom.xml as ignored in Eclipse build ' and click ' Finish '-' OK '
4. Eclipse and MyEclipse may error ' PROJCT configuration is not up-to-date with pom.xml. Run project configuration Update. Follow the above method and right click on "Quick fix" to resolve
5, repeat 2-3 steps to solve other problems
The above method comes from the network and is for reference only.
In the POM configuration maven Plugin hint error "Plugin execution not covered by lifecycle configuration" solution