[
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
