[MASSEMBLY-579] Dependency-filename appended as subdirectory of outputDirectory of dependencySet when unpackOptions/filtered = true

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2, 2.2.1
• Fix Version/s: 2.5.1
• Component/s: filtering
• Environment: Windows 7; OS X 10.6
• Assignee: Kristian Rosenvold
• Reporter: Rune Flobakk
• Created: 27/Oct/11 06:46
• Updated: 29/Oct/14 00:17
• Resolved: 29/Oct/14 00:14

Description

I have attached a minimal project demonstrating the different behavior of unpacking a dependencySet when unpackOptions/filtered is set to either true or false. With value of false, the contents of the dependency is correctly unpacked to the declared outputDirectory, but with filtered=true the contents is unpacked to a subdirectory of outputDirectory with the same name as the dependency's filename.

In the attached project I have declared a dependency to maven-default-skin (randomly choosed artifact). In my assembly descriptor (src/main/assembly/unpack-deps.xml) I have declared the dependency to be unpacked to deps, but the contents of maven-default-skin ends up in the folder 'deps/maven-default-skin-1.0-SNAPSHOT.jar/' in my resulting zip assembly. Changing filtered to false correctly unpacks to the 'deps/' folder.

Issue Links

• duplicates: MASSEMBLY-533 Outputidrectory appended by dependencyset include name on filtered=true
• duplicates: MASSEMBLY-554 DependencySet unpackOptions 'filtered' causes unpack not to work
• is duplicated by: MASSEMBLY-640 Artifact data added to path when lineEnding tag set in dependencySet
• is duplicated by: MASSEMBLY-672 unpack adds the name of the artifact in case of filtered unpack
• is duplicated by: MASSEMBLY-691 dependencySet with filtered option has differents behaviors