You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2007/03/28 19:06:16 UTC
[jira] Updated: (MASSEMBLY-105) need better support for unpack
[ http://jira.codehaus.org/browse/MASSEMBLY-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-105:
---------------------------------
Fix Version/s: (was: 2.2)
2.2-beta-1
> need better support for unpack
> ------------------------------
>
> Key: MASSEMBLY-105
> URL: http://jira.codehaus.org/browse/MASSEMBLY-105
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Sachin Patel
> Assigned To: John Casey
> Fix For: 2.2-beta-1
>
>
> Currently when specifiying a dependency set inside an assembly descriptor, if one requires the unpack element to be true, then the unpacking is restricted to the output directory. I have a scenario in which I need to use the unpack element in conjuction with the outputFileNameMapping element.
> I would like to request that the outputFileNameMapping be treated as a folder to extract into and appended to the outputDirectory.
> So given dependency "foo-1.0.jar", I need a way to extract this into "outputDirectory/foo_1.0/", and since the outputDirectory cannot take properties such as artifactID, and artifactVersion, need a way to plugin this "property support", and making use of the outputFileNameMapping would provide a nice way to handle this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira