You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/02/05 01:13:57 UTC
[jira] Closed: (MNG-3119) Duplicate attached artifacts should not
be allowed.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MNG-3119.
---------------------------
Resolution: Fixed
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.1-alpha-1
2.0.9
Applied with my own modifications to make it an unchecked exception, to add handling code in the DefaultPluginManager (bypassing the Mojo's need to deal with it), and to add tests.
Thanks for the patch, but please next time try to include some sort of unit test to help us verify that the patch accomplishes its goal.
> 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: 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