You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/01/03 12:47:18 UTC
[jira] Updated: (MASSEMBLY-46) artifact classifier not used in
outputFileNameMapping
[ http://jira.codehaus.org/browse/MASSEMBLY-46?page=all ]
Brett Porter updated MASSEMBLY-46:
----------------------------------
Fix Version: 2.1
> artifact classifier not used in outputFileNameMapping
> ---------------------------------------------------------
>
> Key: MASSEMBLY-46
> URL: http://jira.codehaus.org/browse/MASSEMBLY-46
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Environment: Linux
> Reporter: M. van der Plas
> Assignee: Jason van Zyl
> Fix For: 2.1
>
>
> The classifier field of an artifact cannot be specified in the outputFileNameMapping.
> This means that attached Artifacts with the same type cannot be distinguished.
> I have a native code libraries attached to a java jar. Next, I have documentation etc attached to the artifact. All files have type .tgz.
> When I specify a depencySet I end up with only one file, instead of several. This is caused by the fact that classifier is removed from the name of the the original input artifact file.
> The workaround is to rename attached artifacts to a different type (rename .tgz to .tar.gz...).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org