[ https://issues.apache.org/jira/browse/BEAM-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777784#comment-16777784 ]
Michael Luckey commented on BEAM-6726: -------------------------------------- Oh well... I guess I have to try releasing myself and see, where exactly is the problem. I did not use beams release workflow, but just signed the artifacts. And of course sign plugin needs the key to sign with... dunno how that's specified in beams release process... will have a look. Sorry for the inconvenience... > 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 > Affects Versions: 2.11.0 > Reporter: Ahmet Altay > Assignee: Michael Luckey > Priority: Blocker > Fix For: 2.12.0 > > Time Spent: 2h > 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)