[
http://jira.codehaus.org/browse/MASSEMBLY-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88060
]
John Franey commented on MASSEMBLY-178:
---------------------------------------
The documentation is wrong for versions 2.1 and 2.2-SNAPSHOT. The filters
element is really a child of <build> element not the plugin's <configuration>.
To be attached is a patch to the documentation.
I got this to work with maven 2.0.4 and versions 2.1 and 2.2-SNAPSHOT of the
assembly plugin.
I was unable to use your pom with version 2.0 of the assembly plugin because
the goal 'attached' does not apparently exist in that version of the plugin. I
guess when you selected 'version' for this issue report, you didn't mean to
select 2.0.
> filtering doesn't read filter files
> -----------------------------------
>
> Key: MASSEMBLY-178
> URL: http://jira.codehaus.org/browse/MASSEMBLY-178
> 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
> Attachments: 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:
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
