[
https://issues.apache.org/jira/browse/MSOURCES-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795841#comment-17795841
]
Rob Vesse commented on MSOURCES-140:
------------------------------------
This one is also a bit of a ticking time bomb. Just ran into an issue where
all our normal builds (both local and CI/CD) were running fine. But trying to
go through the maven release process fails at the `mvn release:perform` step
due to this duplicate check (not sure what the release plugin is doing to
trigger this)
So there's likely to be a lot of people who upgrade the plugin and don't
encounter the problem until they actually next make a release.
> Build fails when using install deploy
> -------------------------------------
>
> Key: MSOURCES-140
> URL: https://issues.apache.org/jira/browse/MSOURCES-140
> Project: Maven Source Plugin
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Joern
> Priority: Minor
>
> By configuration maven-source-plugin is bound to verify phase.
> When executing commands like mvn install deploy, which includes phase verify
> 2 times, the build fails with error "We have duplicated artifacts attached."
> - it worked with 3.2.1
> When just using mvn deploy it works.
> I know install and deploy together are redundant but in many build pipelines
> it is used that way and maven as such also allows the combination.
> Probably caused by MSOURCES-121
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
