[MASSEMBLY-178] filtering doesn't read filter files

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.2-beta-2
• Environment: Linux icebox 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 i686 athlon i386 GNU/Linux
• Assignee: Unassigned
• Reporter: Paul Jungwirth
• Created: 22/Jan/07 09:37
• Updated: 01/Feb/08 10:37
• Resolved: 05/Jul/07 08:09

Description

The assembly plugin's filtering supports POM properties like ${project.artifactId}, but not properties read from the filter file, contrary to the documentation here:

http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/filtering-some-distribution-files.html

I've attached a sample app demonstrating the problem. You can run it by saying "mvn clean package." It tries to filter a README file with both ${project.artifactId} and ${homer}. ${homer} is defined in filter.properties like this:

homer=woohoo

But when you run the plugin, only ${project.artifactId} is filtered.

Issue Links

• is related to: MASSEMBLY-154 FileSet does not support filtering
• relates to: MASSEMBLY-54 Unable to filter files while creating assembly