Plugin error: execution not covered by lifecycle configuration

by

This is the new behaviour of m2e (which replaced the old m2eclipse plugin). To specify what eclipse should do with the plugin you have to configure the build lifecycle mapping in the project’s pom.xml – or install a connector (which decides if the plugin needs to be executed in an eclipse build or not) if it exists.

As there seems to be no connector for the maven-warpath-plugin yet you have to define the behaviour in the pom. You can use the second eclipse quickfix for this (Permamnently mark goal add-classes in pom.xml as ignored in eclipse build). This will add the following section to your pom:

<build>
    ......
    <pluginManagement>
        <plugins>
            <!--This plugin's configuration is used to store Eclipse m2e settings 
                only. It has no influence on the Maven build itself. -->
            <plugin>
                <groupId>org.eclipse.m2e</groupId>
                <artifactId>lifecycle-mapping</artifactId>
                <version>1.0.0</version>
                <configuration>
                    <lifecycleMappingMetadata>
                        <pluginExecutions>
                            <pluginExecution>
                                <pluginExecutionFilter>
                                    <groupId>
                                        org.appfuse.plugins
                                    </groupId>
                                    <artifactId>
                                        maven-warpath-plugin
                                    </artifactId>
                                    <versionRange>
                                        [2.1.0,)
                                    </versionRange>
                                    <goals>
                                        <goal>add-classes</goal>
                                    </goals>
                                </pluginExecutionFilter>
                                <action>
                                    <ignore></ignore>
                                </action>
                            </pluginExecution>
                        </pluginExecutions>
                    </lifecycleMappingMetadata>
                </configuration>
            </plugin>
        </plugins>
    </pluginManagement>
</build>

You can change the <ignore> action to <execute> if you want to process the plugin in each eclipse build (on import, clean, …).

The plugin configuration is eclipse specific and does not make the pom.xml look nicer – but at least it has no influence on the Maven build….

More Related Contents:

  1. How to solve “Plugin execution not covered by lifecycle configuration” for Spring Data Maven Builds
  2. SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”. error
  3. Maven2: Missing artifact but jars are in place
  4. Eclipse : Maven search dependencies doesn’t work
  5. M2E and having maven generated source folders as eclipse source folders
  6. How do I set the eclipse.ini -vm option?
  7. Failed to resolve version for org.apache.maven.archetypes
  8. m2e lifecycle-mapping not found
  9. maven-dependency-plugin (goals “copy-dependencies”, “unpack”) is not supported by m2e
  10. get rid of POM not found warning for org.eclipse.m2e:lifecycle-mapping
  11. Checkout Maven project from SCM – no connectors
  12. m2Eclipse plugin: What does ‘Resolve Workspace Artifacts’ do?
  13. web.xml is missing and is set to true
  14. No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
  15. Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.5 or one of its dependencies could not be resolved
  16. Maven error “Failure to transfer…”
  17. Maven in Eclipse: step by step installation [closed]
  18. Missing Maven dependencies in Eclipse project
  19. Maven “build path specifies execution environment J2SE-1.5”, even though I changed it to 1.7
  20. How to solve maven 2.6 resource plugin dependency?
  21. Cannot create Maven Project in eclipse
  22. Error: m2e Install In Eclipse
  23. Compiler error “archive for required library could not be read” – Spring Tool Suite
  24. Eclipse/Maven: JUnit tests not compiled when running them
  25. How do I get my Eclipse-Maven project to automatically update its classpath when I change a dependency in my pom.xml file?
  26. Importing a Maven project into Eclipse from Git
  27. How do I start Maven “compile” goal on save in Eclipse?
  28. Best ways to deal with properties values in XML file in Spring, Maven and Eclipses
  29. Running Maven project on Tomcat from Eclipse
  30. Beginner’s Guide to Setup Xuggler

Leave a Comment