Hi.

I have a problem with deployment of my project structure. My case:
I use Maven to build an enterprise project (ear) composed of a war, an ejb-module and a library jar. Each of these projects are fine in MyEclipse until I try to deploy things to my application server (same problem on both JBoss and Glassfish, I guess it is independent of appserver..)
All my projects have tests associated with them, in seperate source-folders and output-folders. My web-project deploys fine. It has default output folder set to WEB-INF/classes and compiles tests to target/test-classes (normal maven structure).
My ejb-project deploys all .class-files. Both the EJB-files and the tests. These are compiled to target/classes and target/test-classes respectively. I can live with this, it's ugly but it works.
However: my dependency on the java-project makes my deployment fail. In particular: I have a /META-INF/persistence.xml in the test-folder of my java-project. This file overwrites the corresponding file in my ejb-project. This makes the deployment fail with error messages from the application server.

Is there some way to exclude the test and test-resources folders from being deployed?
Some kind of workaround?

regards
trond

Unfortunately this is not yet supported by MyEclipse. It is already on our plans for future versions but it was not targeted to any specific release yet.