[jira] [Updated] (BEAM-11068) beam-sdks-java-bom.pom cannot be signed after upgrade to Gradle 6

["Kenneth Knowles (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-11068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-11068:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> beam-sdks-java-bom.pom cannot be signed after upgrade to Gradle 6
> -----------------------------------------------------------------
>
>                 Key: BEAM-11068
>                 URL: https://issues.apache.org/jira/browse/BEAM-11068
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system
>            Reporter: Robin Qiu
>            Assignee: Robin Qiu
>            Priority: P1
>             Fix For: 2.25.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> I am working on creating Beam 2.25.0 RC1. The repo I created (https://repository.apache.org/#stagingRepositories) failed to close because:
> Missing Signature: '/org/apache/beam/beam-sdks-java-bom/2.25.0/beam-sdks-java-bom-2.25.0.pom.asc' does not exist for 'beam-sdks-java-bom-2.25.0.pom'.
> I checked pom files in other modules and their signatures are present, so I think this problem only happens to beam-sdks-java-bom-2.25.0.pom. Also this has not happened in previous releases. I suspect this is caused by the recent upgrade to Gradle 6.
> I found that https://github.com/apache/beam/blob/master/sdks/java/bom/build.gradle does something special. It does not use a generated pom, instead it uses its own template and copies that to sdks/java/bom/build/publications/mavenJava/ as pom-default.xml. When I run the publish task locally, I found in sdks/java/bom/build/publications/mavenJava/ that the pom-default.xml is signed (i.e. pom-default.xml.asc is present), but beam-sdks-java-bom-2.25.0.pom is not signed (i.e. beam-sdks-java-bom-2.25.0.pom.asc is not present) in the output repository.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)