maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <>
Subject [jira] Closed: (MASSEMBLY-312) outputFileNameMapping not respected when the unpack=true
Date Tue, 16 Sep 2008 20:10:48 GMT


John Casey closed MASSEMBLY-312.

    Resolution: Won't Fix

outputFileNameMapping has a default value which will cause all sorts of problems when appended
to outputDirectory automatically in cases where unpack == true. The element name: outputFileNameMapping
should be a hint at its realm of influence: single files. In other words, when the dependency
is NOT unpacked.

The documentation for this element needs to be updated to reflect this, and I'll take care
of that now.

> outputFileNameMapping not respected when the unpack=true
> --------------------------------------------------------
>                 Key: MASSEMBLY-312
>                 URL:
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-2
>            Reporter: Calvin Yu
>            Assignee: John Casey
>             Fix For: 2.2-beta-3
>         Attachments: massembly-312.txt, massembly312-integration-test.patch
> If I configure a dependencySet to unpack = true, the outputFileNameMapping is not respected,
and instead the artifact is decompressed into the output directory.  Looking at the code,
this looks like it'll affect moduleSets as well.
> For example:
> <dependencySet>
>     <outputDirectory>some_directory</outputDirectory>
>     <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping>
>     <unpack>true</unpack>
> </dependencySet>

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