I have a Java project which is separated into 23 sub-projects that are all checked into a subversion repository. When they are checked out (not using the Eclipse SVN tool) there's a `.svn` directory on several levels of each sub-project. Then I run `mvn eclipse:clean eclipse:eclipse` on the whole thing (as these are Maven projects) I can import them into Eclipse and work there. So far, so good.

Here's the problem: When I deploy the project to Tomcat in Eclipse (oh yes, it's a web project) the `.svn` directories are also deployed. I can circumvent this by adding Resource filters in Eclipse (*project properties -> Resource -> Resource Filters -> Add -> Exclude all, Files and folders, All children (recursive), Project Relative Path matches \**\*/.svn) but every time I recreate the projects with maven (which I have to do ever so often) I have to recreate the filters for each of the 23 projects. Is there a better method to exclude resources for the tomcat deployment?

Note: I'm using 

* Java 1.6,
* Eclipse Juno,
* Tortoise SVN 1.7.6 (which comes with Subversion 1.7.4),
* Maven 3.0.3 and
* Tomcat 7.0.35

I am, sadly, not allowed to update anything. An ideal solution for me would be something like a global resource filter in Eclipse or some setting which would make Maven create Eclipse projects with such resource filters already set.