[ 
https://issues.apache.org/jira/browse/BEAM-11813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285328#comment-17285328
 ] 

Chamikara Madhusanka Jayalath commented on BEAM-11813:
------------------------------------------------------

I'm following release instructions here: 

[https://beam.apache.org/contribute/release-guide/#run-build_release_candidatesh-to-create-a-release-candidate]

(see under "Publish staging artifacts")

I expected artifacts to appear under a single Nexus repository.

All artifacts except for "beam-sdks-java-google-cloud-platform-bom-2.28.0.pom" 
did (including signatures for this file): 

[https://repository.apache.org/content/repositories/orgapachebeam-1161/]

[https://repository.apache.org/content/repositories/orgapachebeam-1161/org/apache/beam/beam-sdks-java-google-cloud-platform-bom/2.28.0/]

 

For whatever reason "beam-sdks-java-google-cloud-platform-bom-2.28.0.pom" ended 
up in it's own Nexus repository (which I did not close, hence no public URL). 
If I drop this the bom will be broken ?

 

> beam-sdks-java-google-cloud-platform-bom files ends up in 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
>            Priority: P1
>             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)

Reply via email to