beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amit Sela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1717) Maven release/deploy tries to uploads some artifacts more than once
Date Mon, 27 Mar 2017 17:35:41 GMT

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

Amit Sela commented on BEAM-1717:
---------------------------------

[~davor] {{beam-sdks-java-core}} is OK now, but now the release fails on duplicate in the
Dataflow runner module, I'll dig back in later this week but maybe you could also take a look
there and see if something catches your attention.
We're working our way through this one nicely module-by-module, just a little bit more effort
and we'll get there ;)

> 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
>             Fix For: First stable release
>
>
> 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)

Mime
View raw message