You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christophe Domas (JIRA)" <ji...@codehaus.org> on 2007/05/10 16:50:12 UTC
[jira] Commented: (MASSEMBLY-178) filtering doesn't read filter
files
[ http://jira.codehaus.org/browse/MASSEMBLY-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95562 ]
Christophe Domas commented on MASSEMBLY-178:
--------------------------------------------
The assembly descriptor documentation (http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html) says that it's possible to filter fileSets:
<fileSets>
<fileSet>
<directory/>
<lineEnding/>
<filtered/>
<useStrictFiltering/>
<useDefaultExcludes/>
<outputDirectory/>
<includes/>
<excludes/>
<fileMode/>
<directoryMode/>
</fileSet>
</fileSets>
<files>
<file>
<source/>
<outputDirectory/>
<destName/>
<fileMode/>
<lineEnding/>
<filtered/>
</file>
</files>
but it doesn't work with version 2.2-beta1. Could you fix it? I would prefer that you fix the code more than the doc ;-)
> 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: filt-dist.diff, filter-test.tar.gz, filter-test.zip
>
>
> 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