Thanks for answering.
I tried it, but unfortunally it does not work.
The xxx-ear project does not even have a build path where this can be added. Adding it to the exclusion of the xxx project and the xxx-ejb project has no effect.
BTW: the target dir of the xxx-ejb project does not contain the .svn folders, neither does the deployed xxx-ejb.jar. But the deployed ear and war (both exploded) contain the .svn folders.
WTP unfortunately does not have a generic way of excluding resources like this.
The svn plugins would automatically register .svn folders as "Team Data" and thus not be picked up by anything (at least that's the theory)
I'm starting to think we should add a plugin that allows users to specify which resources should be automatically marked as "derived" and/or "Team Data" so you don't have to install specific team plugins for this.
But that said, the best option today is to install your matching Team plugin provider (in this case .svn) even though you don't actively use it for anything but to make eclipse ignore the .svn folders.
right now we are facing the same problem with our maven project. The integration with eclipse works like a charm but we were surprise to see that during the publishing the .svn are not ignore if they are in the web resource folder (if you don't have the a SVN plugin).
Maven on the other hand excludes them by default, isn't it possible to include this behaviour in the m2eclipse plugin?
This is no different than when classes are compiled by JDT - it will also include .svn/.git if you havent installed eclipse plugin to handle this.
Not sure if m2e can do this "properly" since the requirement is to mark the files as team provider resources to be ignored - and that would be "lying".
feel free to open a bug report and link to it thuogh.