[weld-issues] [JBoss JIRA] Commented: (WELD-835) Make sure all examples have instructions for importing and deploying via JBoss Tools.

[ https://issues.jboss.org/browse/WELD-835?page=com.atlassian.jira.plugin.s... ] Dan Allen commented on WELD-835: -------------------------------- To make sure we're on the same page, I'm assuming that you have the tomcat profile enabled in the Maven settings panel. Otherwise, JBoss Tools shouldn't be seeing this configuration since it's inside of a profile. Is my assumption correct that we are talking about when the tomcat profile is enabled? You are correct that the webapp-tomcat folder is being explicitly defined as the web directory in the configuration. This happens to work in the Maven build because of a quirk (I suppose) in the war plugin, which assumes the resources listed are additive. Meaning, src/main/webapp is assumed to be a web resource always. That's obviously not a good assumption. As it turns out, it's possible to still list src/main/webapp in the Maven configuration. Thus, the configuration in the pom.xml should be: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <configuration> <webResources> <resource> <directory>src/main/webapp-tomcat</directory> <filtering>false</filtering> </resource> <resource> <directory>src/main/webapp-tomcat</directory> <filtering>false</filtering> </resource> </webResources> </configuration> </plugin> Note that it's not one or the other. Both directories are needed for the example to work on Tomcat. This is how we are able to configure the build to target different containers, including AS, Tomcat and Jetty. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira