Fred Bricon created JBSEAM-4896: ----------------------------------- Summary: Seam 2.3 examples don't work OOTB in JBoss Tools 3.3.0.M5 Key: JBSEAM-4896 URL: https://issues.jboss.org/browse/JBSEAM-4896 Project: Seam 2 Issue Type: Bug Affects Versions: 2.3.0.ALPHA Environment: JBoss Tools 3.3.0.M5 Reporter: Fred Bricon When importing seam booking from http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/examples/... into JBoss Tools 3.3.0.M5, 2 kind of maven related errors appear : * "Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile, phase: compile)" is caused by using compilerId=eclipse (This relates to JBIDE-10779). Is there a compelling reason (beside micro compilation optimization) why javac is not used? * "maven-dependency-plugin (goals "copy-dependencies", "unpack") is not supported by m2e" you need to add an explicit lifecycle mapping to trigger the unpack goal (on clean builds, not incremental) : {code:xml} <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.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <versionRange>[1.0,)</versionRange> <goals> <goal>unpack</goal> </goals> </pluginExecutionFilter> <action> <execute><runOnIncremental>false</runOnIncremental></execute> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> </plugins> </pluginManagement> {code} Moreover, if you really really want to unpack resources under your source directory (baaad), and not under target (goood), you should also refine your unpack configuration to skip the META-INF folder (by adding an includes pattern). That gives you : {code:xml} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <executions> <execution> <id>copy-seam-bootstrap</id> <phase>process-resources</phase> <goals> <goal>unpack</goal> </goals> <configuration> <includes>bootstrap/**</includes> <artifactItems> <artifactItem> <groupId>org.jboss.seam</groupId> <artifactId>jboss-embedded-bootstrap</artifactId> <version>${project.version}</version> <type>jar</type> <overWrite>false</overWrite> <outputDirectory>${basedir}/src/test</outputDirectory> </artifactItem> </artifactItems> </configuration> </execution> </executions> </plugin> <plugin> <artifactId>maven-clean-plugin</artifactId> <configuration> <filesets> <fileset> <directory>${basedir}/src/test/bootstrap</directory> </fileset> </filesets> </configuration> </plugin> {code} -- 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