[
http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128828#action_128828
]
Brian Fox commented on MNG-3119:
--------------------------------
I'll revert then and we can rethink this. The forked lifecycle must be dealt
with before we can do this accurately. If we can detect multiple duplicate
attachments from the same lifecycle, then that's probably bad...which is what
you meant. But if a build forks and repeats the same thing, well there's not
much to be done about that in 2.0.x i think.
> Duplicate attached artifacts should not be allowed.
> ---------------------------------------------------
>
> Key: MNG-3119
> URL: http://jira.codehaus.org/browse/MNG-3119
> Project: Maven 2
> Issue Type: Improvement
> Components: General
> Affects Versions: 2.0.7
> Reporter: Paul Gier
> Assignee: John Casey
> Fix For: 2.0.9, 2.1-alpha-1
>
> 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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
