[BEAM-11813] beam-sdks-java-google-cloud-platform-bom files ends up in two nexus repositories

• Type: Bug
• Status: Resolved
• Priority: P0
• Resolution: Fixed
• Affects Version/s: 2.28.0
• Fix Version/s: 2.28.0
• Component/s: build-system, sdk-java-core
• Assignee: Kiley Sok
• Reporter: Chamikara Madhusanka Jayalath
• Created: 14/Feb/21 02:43
• Updated: 16/Sep/21 00:50
• Resolved: 18/Feb/21 04:04

Description

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.