You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2007/07/23 22:24:13 UTC
[jira] Created: (MNG-3119) Duplicate attached artifacts should not
be allowed.
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
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
[jira] Commented: (MNG-3119) Duplicate attached artifacts should
not be allowed.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MNG-3119) Duplicate attached artifacts should not
be allowed.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-3119) Duplicate attached artifacts should not
be allowed.
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated MNG-3119:
---------------------------
Attachment: MNG-3119-maven-project-r558713.patch
Adding a patch that displays a warning message if an attempt is made to attach a duplicate artifact.
I didn't see any existing exception classes that fit this scenario, so I created a new exception class. The exception does not propagate any further than the MavenProjectHelper in this case because I didn't want to break any existing code (plugins, etc.) that may depend on the helper attach artifact methods not throwing an exception.
> 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
> 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
[jira] Updated: (MNG-3119) Duplicate attached artifacts should not
be allowed.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-3119) Duplicate attached artifacts should not
be allowed.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3119:
------------------------------
Fix Version/s: 2.0.x
> 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
> Fix For: 2.0.x
>
> 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
[jira] Reopened: (MNG-3119) Duplicate attached artifacts should not
be allowed.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox reopened MNG-3119:
----------------------------
This exception is propagating up and stopping the build, which is not the intended behavior
> 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
[jira] Commented: (MNG-3119) Duplicate attached artifacts should
not be allowed.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122340 ]
John Casey commented on MNG-3119:
---------------------------------
I'm applying this, with slight modification:
I'm turning the exception class into an unchecked exception, so it can bypass the calling Mojo stack frames and be intercepted by the DefaultPluginManager, which will wrap it as a PluginExecutionException. In trunk, this gives me a binding point for an error reporter. In 2.0.x, it means that the error will simply be reported as-is to the console. In both cases, the wrapped error should be reported in the MavenExecutionResult.
I can't think of a better solution right now than an unchecked exception, even though it's technically more of a configuration problem than a developer's problem (the typical domain for runtime exceptions, since they typically require code changes). We can't really change the throws clause of the MavenProjectHelper methods, since these will create compatibility problems that cannot be amended easily through an aspect (I think), and in any case this would cause major problems for porting the solution to the 2.0.9 codebase.
I'll also include tests before I commit.
> 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: Reviewed Pending Version Assignment
>
> 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
[jira] Updated: (MNG-3119) Duplicate attached artifacts should not
be allowed.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3119:
------------------------------
Patch Submitted: [Yes]
> 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
> 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
[jira] (MNG-3119) Duplicate attached artifacts should not be
allowed.
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-3119) Duplicate attached artifacts should not
be allowed.
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-3119:
-------------------------------
Fix Version/s: (was: 2.1-alpha-1)
2.1-alpha-2
> 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.1-alpha-2
>
> 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
[jira] Updated: (MNG-3119) Duplicate attached artifacts should not
be allowed.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MNG-3119:
---------------------------
Fix Version/s: (was: 2.0.9)
reverted from 2.0.9
> 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.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
[jira] Commented: (MNG-3119) Duplicate attached artifacts should
not be allowed.
Posted by "Sejal Patel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128827#action_128827 ]
Sejal Patel commented on MNG-3119:
----------------------------------
Not sure what the heck is happening here but it seems related to this issue. I just tried to do a release with maven 2.0.9RC3. The goals defined for a release are
<goals>source:jar deploy site site:deploy emarketing-changes:announcement-mail</goals>
However, it looks like it is breaking during the source:jar portion of the release:perform process.
Here is the snippet from the console
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar: /home/sepatel/workspace/webflow-utils/target/checkout/target/webflow-utils-0.3-sources.jar
[WARNING] Duplicate artifact attachment detected. (project: com.turner.emarketing.webflow:webflow-utils:jar:0.3; illegal attachment: com.turner.emarketing.webflow:webflow-utils:java-source:sources:0.3)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error attaching artifact to project: Duplicate attachment.
Embedded error: Duplicate artifact attachment detected. (project: com.turner.emarketing.webflow:webflow-utils:jar:0.3; illegal attachment: com.turner.emarketing.webflow:webflow-utils:java-source:sources:0.3)
> 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
[jira] Commented: (MNG-3119) Duplicate attached artifacts should
not be allowed.
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128825#action_128825 ]
Paul Gier commented on MNG-3119:
--------------------------------
I don't have a problem with the changes from this being reverted and rescheduling this for a future release, since IMO it's a relatively low priority issue. The idea was just to warn the user in case a plugin attaches an artifact with the same name as an existing attached artifact and overwriting it.
> 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
[jira] Updated: (MNG-3119) Duplicate attached artifacts should not
be allowed.
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton updated MNG-3119:
---------------------------------
Fix Version/s: (was: 2.0.x)
Reviewed Pending Version Assignment
> 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
> Fix For: Reviewed Pending Version Assignment
>
> 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