[
https://issues.apache.org/jira/browse/BEAM-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775173#comment-16775173
]
Michael Luckey commented on BEAM-6726:
--------------------------------------
Opened PR [https://github.com/apache/beam/pull/7925]
With this change, I was able to sign projects artifacts. As [~kenn] already
stated, this was triggered by improper configuration on our side. (Thx btw for
those links, Kenn, as those provided the relevant information to understand
this issue)
[~altay] this should render it unnecessary to downgrade for the release. Hope,
no other issues will show up, as I did not test the full release cycle.
> Gradle Publish fails with Gradle 5
> ----------------------------------
>
> Key: BEAM-6726
> URL: https://issues.apache.org/jira/browse/BEAM-6726
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Ahmet Altay
> Assignee: Michael Luckey
> Priority: Blocker
> Fix For: 2.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> cc: [~alanmyrvold] [~kenn]
> :beam-sdks-java-bom:signMavenJavaPublication task fails with an obscure
> error:
> (https://scans.gradle.com/s/mcbb4axlx6agy/failure?openFailures=WzBd&openStackTraces=WzFd#top=0):
> Duplicate key pom-default.xml.asc:xml.asc:asc:null (attempted merging values
> Signature pom-default.xml.asc:xml.asc:asc:null and Signature
> pom-default.xml.asc:xml.asc:asc:null)
> Downgrading to Gradle 4 by reverting
> https://github.com/apache/beam/commit/cadb6f7fabc6faedc6037104338306688f17652f
> works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
