[
https://issues.apache.org/jira/browse/BEAM-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924819#comment-15924819
]
Amit Sela commented on BEAM-1717:
---------------------------------
Once this worked-out, I noticed a duplicate {{test}} jar in
{{beam-sdks-java-core}}.
Not sure what's the issue here, but running maven in debug mode shows that in
the execution of {{maven-install-plugin}} the {{attachedArtifacts}} contain
both {{org.apache.beam:beam-sdks-java-core:test-jar:tests}} and
{{org.apache.beam:beam-sdks-java-core:jar:tests}} which seem to cause the
duplication.
While the {{default-test-jar}} execution id (jar plugin) calls the {{test-jar}}
goal, I wonder if the {{jar}} goal also creates a {{tests}} jar.
> 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: Amit Sela
> 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)
