Chamikara Madhusanka Jayalath created BEAM-11813:
----------------------------------------------------
Summary: beam-sdks-java-google-cloud-platform-bom files ends up
two nexus repositories
Key: BEAM-11813
URL: https://issues.apache.org/jira/browse/BEAM-11813
Project: Beam
Issue Type: Bug
Components: sdk-java-core
Affects Versions: 2.28.0
Reporter: Chamikara Madhusanka Jayalath
Assignee: Kiley Sok
Fix For: 2.28.0
When building the Beam 2.28.0 RC1 I noticed that
"beam-sdks-java-google-cloud-platform-bom-2.28.0" modules related files end up
in two different Apache nexus staging repositories.
(1) beam-sdks-java-google-cloud-platform-bom-2.28.0.pom in it's own repository
(2) Everything else including signature/checksum files for above ends up in the
regular nexus staging repository
Seems like this module was recently added in
[https://github.com/apache/beam/pull/13737]
Not sure why this is happening but I suspect a mis-configuration somewhere.
I believe this blocks release validation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
