正文
解决Maven报Plugin execution not covered by lifecycle configuration
小程序:扫一扫查出行
【扫一扫了解最新限行尾号】
复制小程序
【扫一扫了解最新限行尾号】
复制小程序
来自:http://blog.csdn.net/xxd851116/article/details/25197373
环境 eclipse 4.3.0 maven 3.0.4 m2e 1.4.0 出现场景 以前的老项目,在我的环境(我的环境较新)下,别人老环境不报错。 错误示例一个错误示例,子项目引用了父项目,子项目parent标签处报错如下:Multiple annotations found at this line:- maven-enforcer-plugin (goal "enforce") is ignored by m2e.- Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:aspectj-maven-plugin:1.3.1:compile (execution: default, phase: compile) 解决办法官网给出解释及解决办法:http://wiki.eclipse.org/M2E_plugin_execution_not_covered 这里有人说下面这样也可以解决, 即 <plugins> 标签外再套一个 <pluginManagement> 标签,我试验是成功的:http://stackoverflow.com/questions/6352208/how-to-solve-plugin-execution-not-covered-by-lifecycle-configuration-for-sprin
<build>
<pluginManagement>
<plugins>
<plugin> ... </plugin>
<plugin> ... </plugin>
....
</plugins>
</pluginManagement>
</build> 但是有时候父项目pom不能被修改,可用官网最后给出的解决办法:Window-Perferences-Maven-Lifecycle Mapping 保存如下内容:
<?xml version="1.0" encoding="UTF-8"?>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<goals>
<goal>compile</goal>
</goals>
<versionRange>[1.3,)</versionRange>
</pluginExecutionFilter>
<action>
<ignore />
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata> 记得点击 ”Reload workspace lifecycle mappings metadata“按钮 问题解决。
以前的老项目,在我的环境(我的环境较新)下,别人老环境不报错。
错误示例一个错误示例,子项目引用了父项目,子项目parent标签处报错如下:Multiple annotations found at this line:- maven-enforcer-plugin (goal "enforce") is ignored by m2e.- Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:aspectj-maven-plugin:1.3.1:compile (execution: default, phase: compile) 解决办法官网给出解释及解决办法:http://wiki.eclipse.org/M2E_plugin_execution_not_covered 这里有人说下面这样也可以解决, 即 <plugins> 标签外再套一个 <pluginManagement> 标签,我试验是成功的:http://stackoverflow.com/questions/6352208/how-to-solve-plugin-execution-not-covered-by-lifecycle-configuration-for-sprin
<build>
<pluginManagement>
<plugins>
<plugin> ... </plugin>
<plugin> ... </plugin>
....
</plugins>
</pluginManagement>
</build> 但是有时候父项目pom不能被修改,可用官网最后给出的解决办法:Window-Perferences-Maven-Lifecycle Mapping 保存如下内容:
<?xml version="1.0" encoding="UTF-8"?>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<goals>
<goal>compile</goal>
</goals>
<versionRange>[1.3,)</versionRange>
</pluginExecutionFilter>
<action>
<ignore />
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata> 记得点击 ”Reload workspace lifecycle mappings metadata“按钮 问题解决。
官网给出解释及解决办法:http://wiki.eclipse.org/M2E_plugin_execution_not_covered
这里有人说下面这样也可以解决, 即 <plugins> 标签外再套一个 <pluginManagement> 标签,我试验是成功的:
http://stackoverflow.com/questions/6352208/how-to-solve-plugin-execution-not-covered-by-lifecycle-configuration-for-sprin
<build>
<pluginManagement>
<plugins>
<plugin> ... </plugin>
<plugin> ... </plugin>
....
</plugins>
</pluginManagement>
</build>
<pluginManagement>
<plugins>
<plugin> ... </plugin>
<plugin> ... </plugin>
....
</plugins>
</pluginManagement>
</build>
但是有时候父项目pom不能被修改,可用官网最后给出的解决办法:
Window-Perferences-Maven-Lifecycle Mapping
保存如下内容:
<?xml version="1.0" encoding="UTF-8"?>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<goals>
<goal>compile</goal>
</goals>
<versionRange>[1.3,)</versionRange>
</pluginExecutionFilter>
<action>
<ignore />
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<goals>
<goal>compile</goal>
</goals>
<versionRange>[1.3,)</versionRange>
</pluginExecutionFilter>
<action>
<ignore />
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
记得点击 ”Reload workspace lifecycle mappings metadata“按钮
问题解决。