jira-importer opened a new issue, #212: URL: https://github.com/apache/maven-war-plugin/issues/212
**[Julian Wood](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=woodj)** opened **[MWAR-40](https://issues.apache.org/jira/browse/MWAR-40?redirect=false)** and commented I have many released projects which won't build properly anymore because of this regression. The problem is that if you filter resources to a special dir, and then make that special dir the warSourceDirectory, it doesn't use those filtered files. You just get the original, unfiltered files. An example pom: \<build> \<resources> ... \<resource> \<targetPath>../filtered-webapp-resources\</targetPath> \<filtering>true\</filtering> \<directory>${basedir}/src/main/webapp\</directory> \<includes> \<include>**/log4j.txt\</include> \<include>**/web.xml\</include> \</includes> \</resource> \</resources> \<plugins> \<plugin> \<artifactId>maven-war-plugin\</artifactId> \<executions> \<execution> \<goals> \<goal>war\</goal> \</goals> \<configuration> \<warSourceDirectory>${project.build.directory}/filtered-webapp-resources\</warSourceDirectory> \</configuration> \</execution> \</executions> \</plugin> \</plugins> \</build> While ${project.build.directory}/filtered-webapp-resources has all the correctly filtered resource files, the war plugin seems to ignore its warSourceDirectory. --- **Affects:** 2.0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
