[jbosstools-issues] [JBoss JIRA] (JBIDE-10779) "Plugin execution not covered by lifecycle configuration" for maven-compiler-plugin when importing Seam 2.3 examples

[Fred Bricon (JIRA)]

Fred Bricon created JBIDE-10779:
-----------------------------------

             Summary: "Plugin execution not covered by lifecycle configuration" for maven-compiler-plugin when importing Seam 2.3 examples
                 Key: JBIDE-10779
                 URL: https://issues.jboss.org/browse/JBIDE-10779
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: Build/Releng, maven
    Affects Versions: 3.3.0.M5
            Reporter: Fred Bricon
            Assignee: Fred Bricon
             Fix For: 3.3.0.Beta1


When importing Seam 2.3 examples (ex booking from http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/examples/booking/), Java projects are not configured properly and you get red error markers like 
{quote}Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile, phase: compile){quote}

The problem is some parent configures the maven-compiler-plugin to use compilerId=eclipse, which is not supported out of the box by m2e (it only supports the default compilerId=javac).

To fix this issue, you have to either :
* Modify your parent pom.xml to map the compilerId=eclipse pluginExecution to the org.eclipse.m2e.jdt.javaConfigurator by adding 
{code: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.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <versionRange>[2.0,)</versionRange>
                <goals>
                  <goal>compile</goal>
                  <goal>testCompile</goal>
                </goals>
              <parameters>
                <compilerId>eclipse</compilerId>
              </parameters>
             </pluginExecutionFilter>
             <action>
               <configurator>
                 <id>org.eclipse.m2e.jdt.javaConfigurator</id>
               </configurator>
             </action>
           </pluginExecution>
          </pluginExecutions>
        </lifecycleMappingMetadata>
      </configuration>
    </plugin>
  </plugins>
</pluginManagement>
{code}
* or install m2e-jdt-compiler from  http://download.jboss.org/jbosstools/builds/staging/m2e-jdt-compiler/all/repo/

2nd option is obviously far less intrusive. It requires m2e-jdt-compiler to be made available from a stable URL and added as a build requirement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira