Community
Participate
Working Groups
Mojo execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-antrun-plugin:1.2:run {execution: create-prop} (maven lifecycle phase: initialize) Mojo execution not covered by lifecycle configuration: org.codehaus.mojo:properties-maven-plugin:1.0-alpha-2:read-project-properties {execution: default} (maven lifecycle phase: initialize) An example pom with this problem is here: https://svn.apache.org/repos/asf/aries/trunk/application/application-utils/pom.xml I have IAM 0.13 and a Tycho build from https://www.sonatype.com/~ifedorenko/m2e4m2e/
Assuming you meant "m2e 0.13", this is expected. The idea is that m2e needs to know what to do with all plugin executions bound to "interesting" build lifecycle phases in order to guarantee predictable behaviour. As of now, m2e does not know anything about maven-antrun-plugin and properties-maven-plugin, so it marks these as errors. If the plugin executions are not needed to be able to compile the project and run tests, then you can safely ignore these errors. It is also possible to suppress them via additional configuration elements in pom.xml and I believe there is a quick fix associated with the error markers to help you do that. If the plugin executions are needed to be able to compile the project and run tests... then m2e-users is a good place to discuss possible options.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
