Actually there's a way to deploy test resources in m2e-wtp, using a pom.xml configuration hack :
<profile>
<id>deploy-tests</id>
<!-- This profile is only activated when building in Eclipse with m2e -->
<activation>
<property>
<name>m2e.version</name>
</property>
</activation>
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.4</version>
<configuration>
<webResources>
<resource>
<directory>src/test/resources/</directory>
<targetPath>WEB-INF/classes</targetPath>
</resource>
<resource>
<directory>${project.build.directory}/test-classes/</directory>
<targetPath>WEB-INF/classes</targetPath>
</resource>
</webResources>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
</profile>
This deploy-test profile is automatically enabled when run within eclipse, or using with -Pdeploy-tests in command line.
Normally, we should only reference ${project.build.directory}/test-classes/ here but the processed resources are not always picked up as expected, so, explicitely referencing their source folder (not entirely correct if you expect resource filtering) is the most reliable way to get them copied to target/m2e-wtp/web-resources/. I've tested it deploys as expected on Wildfly 8.1
Fred