[
http://jira.codehaus.org/browse/MASSEMBLY-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruzicka Cestmir updated MASSEMBLY-217:
--------------------------------------
Attachment: massembly-217.patch
A little patch for archive duplicity.
When archiver contains artifacts file, exception is thrown
> <outputFileNameMapping> needs to report collision.
> --------------------------------------------------
>
> Key: MASSEMBLY-217
> URL: http://jira.codehaus.org/browse/MASSEMBLY-217
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Reporter: Kohsuke Kawaguchi
> Fix For: 2.2-beta-3
>
> Attachments: massembly-217.patch
>
>
> If <outputFileNameMapping> maps two or more artifacts into the same name, it
> needs to be reported as an error.
> Maven currently just takes the last one without reporting anything, and as a
> result I didn't notice that my assembly descriptor had a problem until I
> debug the plugin source code.
> This problem is particularly made worse by a broken jar-with-dependencies
> example in [the
> documentation|http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html],
> which says:
> {noformat}
> <dependencySets>
> <dependencySet>
> <outputDirectory></outputDirectory>
> <outputFileNameMapping></outputFileNameMapping>
> <unpack>true</unpack>
> <scope>runtime</scope>
> </dependencySet>
> </dependencySets>
> {noformat}
> ... which maps every dependency to ""
--
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
