Eclipse "Deployment Assembly" including too many jars in war

[bwallis42]

I have a war project that is assembled from a number of other local projects and depencencies, the projects are all maven based builds. (JBoss Developer Studio is 4.0.0.GA running with JDK 1.6.0_24 on a Mac OSX 10.6).

To configure the war to deploy in a jboss 6 server in eclipse I configure the projects and the maven depencencies in the web deployment assembly under the Deployment Assembly tab in the project properties. The problem that I have is that I have to include the maven dependencies in the deployment assembly (of course) but that seems to be including all of the depencencies regardless of the maven dependency scope.

When I build the war in maven only the compile and runtime dependencies are included in the war but when running in jbds  the test and provided depencencies are also (wrongly) being included in the deployed war.

Is there any way to exclude these? They should not be included in the deployment and it means that I am developing and testing with something that is different from what is actually deployed in the real war file and the behaviour can change.

[fbricon]

This is a common issue people have when they haven't installed m2e-wtp. You can grab it from :

http://m2eclipse.sonatype.org/sites/m2e-extras

See this post on m2e-wtp 0.12.0 which should be compatible with JBDS 4.x.

[bwallis42]

I've updated m2e and installed the wtp extras AND stopped using the maven-eclipse-plugin to generate eclipse project files. Now it is working very well.