Hi all, 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. I tried to understand how the Gradle plugins (maven-publish and signing) work and changed a few different configurations in https://github.com/apache/beam/blob/master/sdks/java/bom/build.gradle but that didn't help. Does anyone have context on this issue or have any suggestions that I could try? This is currently blocking the 2.25.0 release. Thanks, Robin
