maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Fovez (JIRA)" <>
Subject [jira] Commented: (MASSEMBLY-178) filtering doesn't read filter files
Date Fri, 06 Jul 2007 09:01:13 GMT


Bertrand Fovez commented on MASSEMBLY-178:


However, the following, based upon the previous, doesn't work :


> filtering doesn't read filter files
> -----------------------------------
>                 Key: MASSEMBLY-178
>                 URL:
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: Linux icebox 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 i686
athlon i386 GNU/Linux
>            Reporter: Paul Jungwirth
>            Priority: Minor
>             Fix For: 2.2-beta-2
>         Attachments: filt-dist.diff, filter-test.tar.gz,
> The assembly plugin's filtering supports POM properties like ${project.artifactId}, but
not properties read from the filter file, contrary to the documentation here:
> 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 like this:
> homer=woohoo
> But when you run the plugin, only ${project.artifactId} is filtered.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message