Supersedes #28577

Comment From: hennr

Hi @snicoll , sorry if I am getting something wrong here, but I just saw that the spring-boot-dependencies artifact on mvn central still uses kotlin.version 1.5.31: https://search.maven.org/artifact/org.springframework.boot/spring-boot-dependencies/2.6.0/pom

The SB 2.6.0 release notes (https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.6-Release-Notes#upgrading-from-spring-boot-25) state that kotlin 1.6.0 is used now though.

Is this a bug or don't I get something correctly here?

Comment From: bclozel

@hennr This file shows the following line for me:

<kotlin.version>1.6.0</kotlin.version>
</properties>
<!-- ... -->
<dependency>
  <groupId>org.jetbrains.kotlin</groupId>
  <artifactId>kotlin-bom</artifactId>
  <version>${kotlin.version}</version>
  <type>pom</type>
  <scope>import</scope>
</dependency>

Comment From: hennr

It does indeed! Strange, so the maven central web-ui seems broken in some way then:

https://search.maven.org/artifact/org.springframework.boot/spring-boot-dependencies/2.6.0/pom grafik

Comment From: wilkinsona

Indeed. When I first go to the page, no source is shown for the pom. If I switch to 2.5.7, it shows the source for 2.5.7's pom. Switching back to 2.6.0 then continues to show the source for 2.5.7. Can you please report this to Sonatype?

Comment From: hennr

@wilkinsona , sure, here you go https://github.com/sonatype-nexus-community/search-maven-org/issues/159

One more question though: Could you check if the artifact upload was completely successful on your end?

I have the exact same behaviour that you described, but what's bugging me is that a click on browse in upper right corner succeeds but a click on the download button fails with a 404.

Comment From: wilkinsona

The two are different URLs:

  • Download: https://search.maven.org/remotecontent?filepath=org/springframework/boot/spring-boot-dependencies/2.6.0/spring-boot-dependencies-2.6.0.pom
  • Browse: https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-dependencies/2.6.0/

I would avoid using search.maven.org when trying to check Maven Central's contents. Going directly to repo1.maven.org is, IMO, the right thing to do as it eliminates the possibility of search.maven.org causing the problem either due to a bug or because its index is stale.

Comment From: hennr

It's been a caching problem on search.maven.org and it's shown correctly now, see https://github.com/sonatype-nexus-community/search-maven-org/issues/159 for details. Thanks for your time and input on this!