[jbosstools-issues] [JBoss JIRA] (JBIDE-10779) "Plugin execution not covered by lifecycle configuration" for maven-compiler-plugin when importing Seam 2.3 examples
Marek Novotny (JIRA)
jira-events at lists.jboss.org
Wed Feb 1 14:39:48 EST 2012
[ https://issues.jboss.org/browse/JBIDE-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663516#comment-12663516 ]
Marek Novotny edited comment on JBIDE-10779 at 2/1/12 2:39 PM:
---------------------------------------------------------------
eclipse compiler was in Seam before 2.3. Anyway I already did a change to javac, but as it has seemed to not affect anything badly, now we can see some javac bug in compiling instrumented wicket classes in wicket example.
{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project wicket-web: Compilation failure
[ERROR] Failure executing javac, but could not parse the error:
[ERROR] An exception has occurred in the compiler (1.6.0_26). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you.
[ERROR] com.sun.tools.javac.code.Symbol$CompletionFailure: class file for javax.persistence.TemporalType not found
[ERROR] -> [Help 1]
{noformat}
so I might need to go back to eclipse compiler in near future :-(
was (Author: manaRH):
eclipse compiler was in Seam before 2.3. Anyway I already did a change to javac, but as it hash seemed to not affect anything badly, now we can see some javac bug in compiling instrumented wicket classes in wicket example.
{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project wicket-web: Compilation failure
[ERROR] Failure executing javac, but could not parse the error:
[ERROR] An exception has occurred in the compiler (1.6.0_26). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you.
[ERROR] com.sun.tools.javac.code.Symbol$CompletionFailure: class file for javax.persistence.TemporalType not found
[ERROR] -> [Help 1]
{noformat}
so I might need to go back to eclipse compiler in near future :-(
> "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
More information about the jbosstools-issues
mailing list