o Although it is bad form to create class files in your source area, it does make development

a lot faster (no build / compile cycle for good containers).  
  So, *.class files that are under WEB-INF/classes in src/webapp 
  will be excluded from the final WAR.  

o This may break builds that rely on this behaviour.
o Ultimately I'd prefer a two phase war process, build the war in target/war and then 
   package it.  Then people could hook in before the packaging to cleanly do whatever they want.


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113203 13f79535-47bb-0310-9956-ffa450edef68

war/plugin.jelly

@@ -42,6 +42,7 @@
       <j:if test="${webSourcesPresent == 'true'}">
         <fileset dir="${maven.war.src}">
         	<exclude name="WEB-INF/web.xml"/>
+        	<exclude name="WEB-INF/classes/**/*.class"/>
         </fileset>
       </j:if>