Community
Participate
Working Groups
Build Identifier: 20110916-0149 m2e version: 1.0.100.20110804-1717 The following plugin definition causes the m2e warning. There is no way to tell m2e to not display this warning (explicit lifecycle-mapping does NOT do the trick). <plugin> <artifactId>maven-enforcer-plugin</artifactId> <version>1.0.1</version> <executions> <execution> <id>enforcer-execution</id> <goals> <goal>enforce</goal> </goals> <configuration> <rules> <requireJavaVersion> <version>1.6.0</version> </requireJavaVersion> <requireMavenVersion> <version>2.1</version> </requireMavenVersion> <requireReleaseDeps> <message>message</message> <onlyWhenRelease>true</onlyWhenRelease> </requireReleaseDeps> </rules> </configuration> </execution> </executions> </plugin> Reproducible: Always Steps to Reproduce: 0. Start from clean m2e project (no warning) 1. Add the plugin definition 2. Update Maven project configuration in m2e 3. The warning is displayed in Eclipse, no quick fix available (and no workaround possible)
Created attachment 205664 [details] sample project that demonstrates <ignore/> mapping Attached sample project does not have any enforcer-related workings when imported in current m2e 1.1.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/