get rid of POM not found warning for org.eclipse.m2e:lifecycle-mapping

My team works around this problem by wrapping the relevant configuration in a profile:

<profile>  <id>only-eclipse</id>  <activation>    <property>      <name>m2e.version</name>    </property>  </activation>  <build>    <pluginManagement>      <plugins>        <plugin>          <groupId>org.eclipse.m2e</groupId>          <artifactId>lifecycle-mapping</artifactId>          <version>1.0.0</version>          <configuration>            ...          </configuration>        </plugin>      </plugins>    </pluginManagement>  </build></profile>

This a known bug with WONTFIX resolution. The suggested solution is the simplest in my opinion:

mvn archetype:generate -DgroupId=org.eclipse.m2e -DartifactId=lifecycle-mapping \ -Dversion=1.0.0 -DarchetypeArtifactId=maven-archetype-mojo

and install this project.

m2eclipse 1.7.0 introduced an alternative, namely an XML processing instruction.

In the original example, you would simply “annotate” every <execution> of the maven-processor-plugin’s process goal with

<?m2e execute?>

See the release notes for more details on the syntax and further options.