Usually I can find a full dist of the spring releases at: https://maven.springframework.org/release/org/springframework/spring/ 5.2.4 does not seem to have been posted despite most of the modules now being available on Maven central.

Comment From: snicoll

Thanks for the report @JohnZ1385. This looks like a regression introduced by a change in our build script.

FTR, the canonical url for that repo is https://repo.spring.io/release/org/springframework/spring/

Comment From: bclozel

The last successful SNAPSHOT deploy was done on February 7th, which leads me to think that the repository declaration done in 02e90a8645d34389d737718d72573947110e681a might have something to do with this problem.

Comment From: sbrannen

The last successful SNAPSHOT deploy was done on February 7th, which leads me to think that the repository declaration done in 02e90a8 might have something to do with this problem.

@wilkinsona, thoughts?

Comment From: wilkinsona

I can’t explain why that repository declaration would cause a publishing problem. The repository declaration should only affect dependency resolution and only dependencies in the io.spring.asciidoctor group at that. It would be particularly bizarre for it to only affect one module as well.

That said, it’s impossible to rule it out as the Bamboo Artifactory integration is a black box that could be doing pretty much anything.

Comment From: wilkinsona

The build logs show the artifacts being deployed:

build   28-Feb-2020 17:10:46    Deploying artifact: https://repo.spring.io/libs-snapshot-local/io/spring/asciidoctor/spring/5.2.5.BUILD-SNAPSHOT/spring-5.2.5.BUILD-SNAPSHOT-dist.zip
build   28-Feb-2020 17:10:53    Deploying artifact: https://repo.spring.io/libs-snapshot-local/io/spring/asciidoctor/spring/5.2.5.BUILD-SNAPSHOT/spring-5.2.5.BUILD-SNAPSHOT-docs.zip
build   28-Feb-2020 17:10:56    Deploying artifact: https://repo.spring.io/libs-snapshot-local/io/spring/asciidoctor/spring/5.2.5.BUILD-SNAPSHOT/spring-5.2.5.BUILD-SNAPSHOT-schema.zip
build   28-Feb-2020 17:10:56    Deploying artifact: https://repo.spring.io/libs-snapshot-local/io/spring/asciidoctor/spring/5.2.5.BUILD-SNAPSHOT/spring-5.2.5.BUILD-SNAPSHOT.pom

Note the io/spring/asciidoctor path. I can’t explain why that’s happening. It looks like a bug in the Artifactory Bamboo integration where it’s interpreting a restriction on what group should be available from a repository as the group that should be used for publishing. Fixing that is out of our control and may take some time. The quickest option may be to remove the custom repository declaration and copy the Asciidoctor extension into https://repo.spring.io/libs-spring-framework-build instead.

Comment From: wilkinsona

I can explain it now and it was my fault. Sorry. It should be includeGroup rather than group when configuring the mavenContent.

Comment From: sbrannen

Thanks for figuring out the solution, @wilkinsona! 👍

We'll get that fixed.

Comment From: sbrannen

Distribution zip files are once again being published.

https://repo.spring.io/snapshot/org/springframework/spring/5.2.5.BUILD-SNAPSHOT/

Comment From: snicoll

And the proper zips have been staged for 5.2.5 as well.

Comment From: sbrannen

And the proper zips have been staged for 5.2.5 as well.

Indeed... staged and now available: https://repo.spring.io/release/org/springframework/spring/5.2.5.RELEASE/