- I published a module metaconfig-core 0.3.2 in April, all was fine
- When publishing metaconfig-core 0.3.3 in May, I forgot to bump of the version in the build so it got published as 0.3.2.
- The accidental 0.3.2 in May release overwrote the jars for the 0.3.2 release in April
- I expected sonatype to reject my 0.3.2 May release
In my local cache, I have files from April 22
ls -al ~/.coursier/cache/v1/https/repo1.maven.org/maven2/com/geirsson/metaconfig-core_2.11/0.3.2
drwxr-xr-x 14 ollie staff 476 May 25 15:22 .
drwxr-xr-x 14 ollie staff 476 May 26 23:49 ..
rw-r r- 1 ollie staff 189 Apr 22 18:23 metaconfig-core_2.11-0.3.2-javadoc.jar
rw-r r- 1 ollie staff 11045 Apr 22 18:23 metaconfig-core_2.11-0.3.2-sources.jar
rw-r r- 1 ollie staff 179336 Apr 22 18:23 metaconfig-core_2.11-0.3.2.jar
rw-r r- 1 ollie staff 2628 Apr 22 18:23 metaconfig-core_2.11-0.3.2.pom
rw-r r- 1 ollie staff 40 Apr 22 18:23 metaconfig-core_2.11-0.3.2.pom.sha1
On Maven, the jars are from May 23rd: https://repo1.maven.org/maven2/com/geirsson/metaconfig-core_2.11/0.3.2/
I must have done something wrong when publishing metaconfig-core 0.3.2 in April. But in that case,
- how come the artifacts got synced to Maven Central? I thought releases on Maven Central were immutable.
- could sonatype provide clearer warnings that I'm overwriting an existing release?