[MASSEMBLY-293] <fileSets> not filtered in multimodule build, but <files> are

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2-beta-2
• Fix Version/s: 2.2-beta-3
• Environment: Windows XP
• Assignee: John Dennis Casey
• Reporter: Torsten Reinhard
• Created: 06/Mar/08 11:34
• Updated: 01/Feb/09 10:35
• Resolved: 11/Sep/08 14:40

Description

Filtering doesn´t work in a multimodule build if I use <fileSet> instead of <files> - if I build the module separately, it works....

Shouldn´t the behaviour be the same? I have not looked into the code, but I expect one thing is collection the files (however the filelist is expressed), the other is filtering them. It seems, as the separation of functionality is mixed in here?

See the attached file(s) as example.

Issue Links

• duplicates: MASSEMBLY-340 Filtering doesn't work for multimodule assembly builds
• is duplicated by: MASSEMBLY-230 <fileset> not filtering resources, but <files> does filter
• is duplicated by: MASSEMBLY-322 Filtering in filesets in multimodule build does not work
• relates to: MASSEMBLY-329 Filter fail to initialize when build from parent pom while assembly is in child pom