[ 
http://jira.codehaus.org/browse/MASSEMBLY-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101600
 ] 

Mark Diggory commented on MASSEMBLY-178:
----------------------------------------

It appears that moduleSets cannot be filtered either.
<pre><code>
     <moduleSet>
         <includes>
            <include>*:war</include>
         </includes>
         <binaries>
            <includeDependencies>false</includeDependencies>
            <outputDirectory>webapps/${artifactId}</outputDirectory>
            <unpack>true</unpack>
                <unpackOptions>
                        <filtered>true</filtered>
                </unpackOptions>
         </binaries>
      </moduleSet>
</code></pre>

fails on Maven 2.0.7 and Assembly-plugin 2.2-beta-2-SNAPSHOT. I have a web.xml 
with a ${property} that will not get filtered when I have evidence all other 
<files> are filtered appropriately.

> 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
>             Fix For: 2.2-beta-2
>
>         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

        

Reply via email to