[MASSEMBLY-554] DependencySet unpackOptions 'filtered' causes unpack not to work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.2
• Component/s: filtering
• Environment: Ubuntu 10.10 Linux, x86-64.
• Assignee: Kristian Rosenvold
• Reporter: Dave Combs
• Created: 31/Mar/11 12:27
• Updated: 06/Jan/16 20:01
• Resolved: 29/Oct/14 00:15

Description

In 2.2-beta-4, the dependencySet option 'filtered' does not appear to work. Files from a dependency end up in the right place (under / in the fragment below), but the filters are not applied. In 2.2 it is worse--the files are correctly filtered, but a directory of the same name as the archive from which they came (com.kaazing.gateway.assembly.core.tar.gz below) is included in the output under /, rather than just the contents of the archive, and the filtered files appear there. It's as though the archive is exploded in place under its own name.

<dependencySet>
<outputDirectory>/</outputDirectory>
<unpack>true</unpack>
<unpackOptions>
<filtered>true</filtered>
</unpackOptions>
<includes>
<include>com.kaazing.gateway.core:com.kaazing.gateway.assembly.core:tar.gz:bin</include>
</includes>
</dependencySet>

This makes the filtering option essentially unusable, since I can't find a way to eliminate this top-level directory creation.

Issue Links

• duplicates: MASSEMBLY-533 Outputidrectory appended by dependencyset include name on filtered=true
• is duplicated by: MASSEMBLY-579 Dependency-filename appended as subdirectory of outputDirectory of dependencySet when unpackOptions/filtered = true
• is duplicated by: MASSEMBLY-672 unpack adds the name of the artifact in case of filtered unpack
• relates to: MASSEMBLY-327 Using filtered within dependencySet unpackOptions