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
o Documented the new property in properties.xml
In some cases it might be different from the war dir, so this allows one to
change it in its project.properties file.
It defaults to ${maven.war.build.dir}/${pom.artifactId}.
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113164 13f79535-47bb-0310-9956-ffa450edef68