[
https://issues.apache.org/jira/browse/BEAM-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031221#comment-16031221
]
Jean-Baptiste Onofré commented on BEAM-1717:
--------------------------------------------
I found that the {{maven-shade-plugin}} is the source of the problem:
https://github.com/gatling/maven-shade-plugin/blob/master/src/main/java/org/apache/maven/plugins/shade/mojo/ShadeMojo.java#L537
As the shade plugin attach the test artifact, and do as well, it explains why
we have two artifacts attached to the module.
I'm evaluating two possible solutions:
1. filter/exclude the test artifact in the {{maven-shade-plugin}} configuration
2. don't attach the test artifact in our {{pom.xml}} and let the shade plugin
does it
> Maven release/deploy tries to uploads some artifacts more than once
> --------------------------------------------------------------------
>
> Key: BEAM-1717
> URL: https://issues.apache.org/jira/browse/BEAM-1717
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Amit Sela
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
>
> Running maven {{release}} or {{deploy}} causes some artifacts to deploy more
> than once which fails deployments to release Nexus.
> While this is not an issue for the Apache release process (because it uses a
> staging Nexus), this affects users who wish to deploy their own fork.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
