Tamas Cserveny created MASSEMBLY-672:
----------------------------------------
Summary: unpack adds the name of the artifact in case of filtered
unpack
Key: MASSEMBLY-672
URL: https://jira.codehaus.org/browse/MASSEMBLY-672
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.4
Reporter: Tamas Cserveny
In case I use unpack=true with unpackOptions.filtered=true, then the dependency
will land in a file named after the
"groupId/artifactId/type/classifier/version".
By removing the filtered tag, the dependency will be put into the right
outputDirectory.
Example:
{code:xml}
<dependencySets>
<dependencySet>
<outputDirectory>/</outputDirectory>
<includes>
<include>groupId:artifactId:zip</include>
</includes>
<unpack>true</unpack>
<unpackOptions>
<excludes>
<exclude>**/*.xml</exclude><!-- unpack will include those -->
<exclude>**/*.cfg</exclude>
</excludes>
</unpackOptions>
<useProjectArtifact>false</useProjectArtifact>
<filtered>true</filtered>
</dependencySet>
</dependencySets>
{code}
Will generate a dir called "groupId.artifactId-2.0.0-SNAPSHOT.zip/".
The output directory is completely ignored in this case, if I would specify "X"
inside, the above directory won't land in x instead it will land in the above
generated dir.
Cheers,
Tamas
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
