[
https://issues.apache.org/jira/browse/BEAM-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774714#comment-16774714
]
Ahmet Altay commented on BEAM-6726:
-----------------------------------
> https://github.com/gradle/gradle/issues/8213
This one led me to try with Gradle 4, and the first link was duplicated to this
one. I could not find any other information anywhere else. I tried the
suggestion on the issue
(https://github.com/gradle/gradle/issues/8213#issuecomment-453278398) and it
did not work weither.
Question: Could we revert this change in the release branch? Would use of
Gradle 4 result in different beam artifacts? I am guessing not unless our
artifacts depends on the build tool we use.
> 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
> Priority: Blocker
> Fix For: 2.11.0
>
>
> 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)
