[MWAR-311] Filtering of resources broken in version 2.4

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4
• Fix Version/s: 2.5
• Component/s: filtering
• Environment: mac os x 10.9.2, Maven 3.1.1, Maven 3.2.1
• Assignee: Karl Heinz Marbaise
• Reporter: Evan Brodie
• Created: 14/Mar/14 14:06
• Updated: 25/Jun/14 13:50
• Resolved: 10/Jun/14 03:02

Description

It appears that resource filtering by version 2.4 of the maven-war-plugin is broken. In filtered resource files in the generated WAR directory by Maven, only the properties specified by the Maven build itself (ie, properties hard-coded in pom.xml) will appear in the resources, but not those specified as filters inside of the <filters> tag of <build>. However, the resources file that appear in target/classes will indeed have full filtering applied to it. This behaviour was working as of version 2.3 and earlier (as in, the app.properties file inside both the WAR and the classes directories will have filtering fully applied).

I created a Github repo with a very simple code that can easily reproduce the bug, which reproduction steps and further description. Please check it out here: https://github.com/ecbrodie/mwp-filter-bug

Until this bug is fixed, users like I that rely on filtering to be applied to their classpath resources are forced to use version 2.3 or earlier.

This bug was reproduced on Mac OS X 10.9.2 using both Maven 3.1.1 and 3.2.1.

Issue Links

• depends upon: MWAR-305 Filtering doesn't work as expected after switching from maven-filtering:1.0-beta-2 to maven-filtering:1.1