[
http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MNG-3119:
---------------------------
Attachment: build.log
See the attached build log for the exception. The notable thing here is that
the duplicated attachment is coming from a forked lifecycle. IMO the user can't
control this and it shouldn't even be a warning in that case. They'll be
looking for something they can't do anything about. We may want to consider not
doing this.
> 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
