m2e fix – Plugin execution not covered by lifecycle configuration

I mainly use Apache Maven 2.2.1 via m2e plugin inside Eclipse. This time, I develop software using amazing JBoss 7.

Recently, I decided to use JBoss Logging and JBoss Logging Tools in my projects, in order to create my custom type-safe Logger. After reading JBossLoggingTooling, I add the required configuration for “maven-compiler-plugin” and “maven-processor-plugin” in my pom.xml. Immediately, I noticed 2 errors  in Markers View of my Eclipse. The errors were the following:

Plugin execution not covered by lifecycle configuration: org.bsc.maven:maven-processor-plugin:2.0.2:process (execution: process, phase: generate-sources)    pom.xml    /human-mind    line 260    Maven Project Build Lifecycle Mapping Problem

Plugin execution not covered by lifecycle configuration: org.bsc.maven:maven-processor-plugin:2.0.2:process-test (execution: process-test, phase: generate-test-sources)    pom.xml    /human-mind    line 275    Maven Project Build Lifecycle Mapping Problem

Both errors are related to m2e plugin and caused because m2e has changed how handles the plugin execution (please check related M2E wiki).  I fix it by adding the following pluginManagement configuration inside my pom.xml:

<pluginManagement>
  <plugins>
    <plugin>
      <groupId>org.eclipse.m2e</groupId>
      <artifactId>lifecycle-mapping</artifactId>
      <version>1.0.0</version>
      <configuration>
        <lifecycleMappingMetadata>
          <pluginExecutions>
            <pluginExecution>
              <pluginExecutionFilter>
                <groupId>org.bsc.maven</groupId>
                <artifactId>maven-processor-plugin</artifactId>
                <versionRange>[2.0.2,)</versionRange>
                <goals>
                  <goal>process</goal>
                </goals>
              </pluginExecutionFilter>
              <action>
                <execute >
                  <runOnIncremental>false</runOnIncremental>
                </execute >
              </action>
            </pluginExecution>
            <pluginExecution>
              <pluginExecutionFilter>
                <groupId>org.bsc.maven</groupId>
                <artifactId>maven-processor-plugin</artifactId>
                <versionRange>[2.0.2,)</versionRange>
                <goals>
                  <goal>process-test</goal>
                </goals>
              </pluginExecutionFilter>
              <action>
                <execute >
                  <runOnIncremental>false</runOnIncremental>
                </execute >
              </action>
            </pluginExecution>
          </pluginExecutions>
        </lifecycleMappingMetadata>
      </configuration>
    </plugin>
  </plugins>          
</pluginManagement>

If you want to use JBoss Logging Tools and m2e, then you have to make the above change in order to avoid annoying errors in Eclipse Marker View. This is a m2e problem and you may face it in any case you need to define/change the execution of a Maven plugin.

After add the above configuration in pom.xml, then you will see the same error that I mentioned in my previous post (follow the same procedure).

Regards,
Adrianos Dadis.

Democracy requires Free Software

Advertisements

About Adrianos Dadis

Building Big Data & Streaming processing solutions in telcos business domain. Interested in distributed systems and enterprise integration.
This entry was posted in Java, JBoss, Software Development and tagged , , , . Bookmark the permalink.

Post your thought

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s