[
https://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MNG-3119.
---------------------------------
Resolution: Won't Fix
Assignee: Benson Margulies (was: John Casey)
I've reached the conclusion that this is desirable and useful behavior.
Consider the maven-shade-plugin. It eats the output of the jar plugin and
produces a replacement. It absolutely should supply a new file that replaces
the old file.
If a user creates multiple executions that produce the same resulting artifact,
the last one should win.
That set of semantics are not currently implemented, but I have another JIRA in
which to implement them.
> Duplicate attached artifacts should not be allowed.
> ---------------------------------------------------
>
> Key: MNG-3119
> URL: https://jira.codehaus.org/browse/MNG-3119
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: General
> Affects Versions: 2.0.7
> Reporter: Paul Gier
> Assignee: Benson Margulies
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: build.log, MNG-3119-maven-project-r558713.patch
>
>
> Currently, a project allows duplicate artifacts to be attached. This causes
> the second and other additional artifacts to overwrite the first attached
> artifact. This occurs during the package, install, and deploy phases.
> This can be reproduced by adding three instances of the source plugin (with
> different ids) to a project build configuration. The 2nd plugin will
> overwrite the first, and the third will overwrite the second.
> The desired behaviour is that the user should receive a warning or error when
> this happens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
