[MASSEMBLY-46] artifact classifier not used in outputFileNameMapping

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1
• Environment: Linux
• Assignee: Allan Q. Ramirez
• Reporter: M. van der Plas
• Created: 27/Dec/05 09:38
• Updated: 07/Mar/06 05:03
• Resolved: 07/Mar/06 05:03

Description

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...).

Issue Links

• is duplicated by: MASSEMBLY-18 Assembly plugin does'nt use classifier for dependencies