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

["Kristian Rosenvold (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MASSEMBLY-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Rosenvold updated MASSEMBLY-579:
-----------------------------------------

    Fix Version/s: 2.5.1

> Dependency-filename appended as subdirectory of outputDirectory of dependencySet when unpackOptions/filtered = true
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-579
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-579
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>          Components: filtering
>    Affects Versions: 2.2, 2.2.1
>         Environment: Windows 7
> OS X 10.6
>            Reporter: Rune Flobakk
>             Fix For: 2.5.1
>
>         Attachments: assembly-plugin-bug-demo.zip
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)