[MASSEMBLY-230] <fileset> not filtering resources, but <files> does filter

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.2-beta-1
• Environment: Windows XP Maven 2.0.5
• Assignee: John Dennis Casey
• Reporter: Mick Knutson
• Created: 17/Aug/07 11:47
• Updated: 06/Jan/16 20:01
• Resolved: 25/Sep/08 15:14

Description

In my assembly descriptor, this does not filter my resources:

<fileSet>
<directory>${basedir}/src/main/resources/deploy</directory>
<filtered>true</filtered>
<useStrictFiltering>true</useStrictFiltering>
<outputDirectory>/</outputDirectory>
<includes>
<include>*.sh</include>
<include>*.bat</include>
</includes>
<fileMode>0544</fileMode>
</fileSet>

But this DOES filter the same resources just fine:

<files>
<file>
<source>${basedir}/src/main/resources/deploy/deploy.sh.txt</source>
<outputDirectory>deploy</outputDirectory>
<destName>test.sh</destName>
<filtered>true</filtered>
<lineEnding>unix</lineEnding>
<fileMode>0554</fileMode>
</file>
</files>

I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.

A workaround is to just specify each file individually, but I have dozens of files and the descriptor is going to get quite cluttered.

Issue Links

• duplicates: MASSEMBLY-293 <fileSets> not filtered in multimodule build, but <files> are
• relates to: MASSEMBLY-329 Filter fail to initialize when build from parent pom while assembly is in child pom
• relates to: MASSEMBLY-154 FileSet does not support filtering