Our internal Maven repo is mirroring Maven Central and for some unknown reason, spring-jcl:6.0.7 artifact doesn't show up. This can also be seen here:
https://mvnrepository.com/artifact/org.springframework/spring-jcl --> no 6.0.7 folder
Nevertheless, the artifact itself seems to exist:
https://repo1.maven.org/maven2/org/springframework/spring-jcl/6.0.7/
Any chance to trigger a rebuild of the indexes?
Comment From: bclozel
I think the situation with mvnrepository.com is completely unrelated to your problem. This is a third party website that indexes Maven Central, often with some delay. For example, spring-context is also missing from that search engine.
The spring-jcl artifact seems to be fine on Maven Central so I guess there is a problem with your mirror? Could you wipe this part on your mirror and trigger a resolution of that artifact again?
Comment From: ratepay-sstein
We solved it now on our side by adding https://repo.spring.io/release/ to our list of mirrored repositories and now it works. Still, I think there must be a more general problem as this used to work without this work-around for years.
Comment From: bclozel
I don't think adding repo.spring.io as a mirror for releases is the right call as anonymous downloads will be restricted in the future, if not already. I can't explain why you're seeing this behavior on your side, because artifacts are being resolved as they should for numerous people and all our CI builds.
I'm closing this issue as it's most likely linked to a mirroring issue.
Comment From: ratepay-sstein
Now it is also available at, so probably some temporal issue somewhere in the chain: https://mvnrepository.com/artifact/org.springframework/spring-jcl/6.0.7
Comment From: bclozel
Again, mvnrepository.com is not affiliated in any way with Sonatype's Maven Central repository. This is a third party website that indexes the central repository (and others) for search. The presence or absence of an artifact there does not mean anything about the actual resolution of artifacts on Maven Central.