maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Combs (JIRA)" <>
Subject [jira] Commented: (MASSEMBLY-554) DependencySet unpackOptions 'filtered' causes unpack not to work
Date Thu, 31 Mar 2011 23:24:22 GMT


Dave Combs commented on MASSEMBLY-554:

I tried setting <outputFileNameMapping></outputFileNameMapping>, and while it
results in the right data for the test case, if the test pulls in an archive (e.g. JAR file)
from inside the .tar.gz, the structure of that archive is then messed up (the size is wrong,
it seems to have malformed content, etc.)  So that possible workaround isn't valid.

> DependencySet unpackOptions 'filtered' causes unpack not to work
> ----------------------------------------------------------------
>                 Key: MASSEMBLY-554
>                 URL:
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>         Environment: Ubuntu 10.10 Linux, x86-64.  
>            Reporter: Dave Combs
>         Attachments:
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message