|Re: [m2e-users] Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile, phase: compile)|
On 11/02/2011 12:24 PM, Vegard B. Havdal wrote:
On Nov 2, 2011, at 12:14 PM, Guillaume Polet wrote:* Is there a way to simply remove all these Errors M2E reports (again a setting in Eclipse, a preference somewhere)?See this ticket: https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414 I really hope someone who knows Eclipse plugin development steps up and fixes this, it seems to affect a bunch of people. Vegard
Storing this information in POM sure looks ugly, but there are important reasons to do that:
1. POMs are shared across teams through Maven repositories and through SCMs. Eclipse settings are not. m2e is supposed to generate a complete, working eclipse project configuration no matter where you pull the project from. The resulting dotfiles (.project, .classpath, .settings/*) are transient and workspace specific. Sharing the across the team through SCM is _not_ recommended because it does more harm than good.
2. POMs are inherited. If the lifecycle mapping is placed outside of POM, either you need to do set it for each and every module separately, which is clearly unacceptable, or implement a mechanism of sharing and inheritance of these settings between module parallel to what is already done with POMs. This is not a workable solution either.
If you can't live with having this information in the POM, you need to create an eclipse plugin that will provide lifecycle mapping for the plugins that your project / company uses. Everyone in your team needs to install it, or get it preinstalled in their Eclipse when they start working on a project, and everything will be fine. All the scary error markers will go away :)
Back to the top