[ https://jira.codehaus.org/browse/MASSEMBLY-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated MASSEMBLY-554: ----------------------------------------- Fix Version/s: 2.5.1 > DependencySet unpackOptions 'filtered' causes unpack not to work > ---------------------------------------------------------------- > > Key: MASSEMBLY-554 > URL: https://jira.codehaus.org/browse/MASSEMBLY-554 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: filtering > Affects Versions: 2.2 > Environment: Ubuntu 10.10 Linux, x86-64. > Reporter: Dave Combs > Fix For: 2.5.1 > > Attachments: example.zip > > > 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 was sent by Atlassian JIRA (v6.1.6#6162)