Problem
The maven-metadata.xml file for the sbt-api-mappings_2.12_1.0 artifact on Maven Central only lists 6 versions:
3.0.2+103-c718b20c
3.0.2+104-3e380bbc
3.0.2+117-b2474ef6
3.0.2+117-ff606f62
3.0.2+117-16d751e1
3.0.2+117-660b5255
However, the actual directory listing at repo1.maven.org contains many more published versions, including clean releases like 3.0.2, 3.0.1, 3.0.0, 2.1.0, 2.0.2, 2.0.1, 2.0.0, etc.
You can verify this by comparing:
Impact
Tools that rely on maven-metadata.xml to discover available versions (like Coursier, which is used by sbt for dependency resolution) cannot see the clean release versions. This causes version update tools to fail because only the +NNN-HASH dynver-style versions are visible.
For example, trying to update from 3.0.2 fails because the only "available" versions are 3.0.2+103-c718b20c, etc., which have a different version shape.
Likely cause
The maven-metadata.xml appears to have been regenerated or overwritten at some point and now only reflects the most recent dynver-style publishes. The clean release versions (published earlier) were dropped from the metadata.
Suggested fix
Republish the metadata or request Maven Central to rebuild the maven-metadata.xml for this artifact so it includes all published versions.
Problem
The
maven-metadata.xmlfile for thesbt-api-mappings_2.12_1.0artifact on Maven Central only lists 6 versions:However, the actual directory listing at repo1.maven.org contains many more published versions, including clean releases like
3.0.2,3.0.1,3.0.0,2.1.0,2.0.2,2.0.1,2.0.0, etc.You can verify this by comparing:
Impact
Tools that rely on
maven-metadata.xmlto discover available versions (like Coursier, which is used by sbt for dependency resolution) cannot see the clean release versions. This causes version update tools to fail because only the+NNN-HASHdynver-style versions are visible.For example, trying to update from
3.0.2fails because the only "available" versions are3.0.2+103-c718b20c, etc., which have a different version shape.Likely cause
The
maven-metadata.xmlappears to have been regenerated or overwritten at some point and now only reflects the most recent dynver-style publishes. The clean release versions (published earlier) were dropped from the metadata.Suggested fix
Republish the metadata or request Maven Central to rebuild the
maven-metadata.xmlfor this artifact so it includes all published versions.