You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2017/05/04 08:02:04 UTC

[jira] [Commented] (BEAM-2169) Release deploy to Nexus fail due to duplicate test jar artifact

    [ https://issues.apache.org/jira/browse/BEAM-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996318#comment-15996318 ] 

Jean-Baptiste Onofré commented on BEAM-2169:
--------------------------------------------

We notice this behavior on another module too (detected while deploying release artifacts on a release repository on local Nexus). I will take a look with Dan.

> Release deploy to Nexus fail due to duplicate test jar artifact
> ---------------------------------------------------------------
>
>                 Key: BEAM-2169
>                 URL: https://issues.apache.org/jira/browse/BEAM-2169
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Kobi Salant
>            Assignee: Daniel Halperin
>
> google-cloud-dataflow-java runner module creates test jar artifact in two different maven steps. The first in the normal jar plugin and the second during the shading phase.
> The shading plugin replaces the original test jar file so actually we are left with one file but when maven deploys the artifacts, the same file is deployed twice and nexus default rule is to fail when trying to overwrite a release artifact.
>   



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)