Support -SNAPSHOT deployment

[vlsi]

Expected and Results

Central Portal expects -SNAPSHOT in file names while Gradle generates timestamp-based versions.

The error is as follows

47 failed Component Validations

pkg:maven/org.qubership.profiler/plugin-generator@1.0.0-SNAPSHOT
33
File name 'plugin-generator-1.0.0-20250418.152138-1-javadoc.jar' is not valid
File name 'plugin-generator-1.0.0-20250418.152138-1-javadoc.jar.md5' is not valid
File name 'plugin-generator-1.0.0-20250418.152138-1-javadoc.jar.sha1' is not valid
File name 'plugin-generator-1.0.0-20250418.152138-1-javadoc.jar.sha256' is not valid
File name 'plugin-generator-1.0.0-20250418.152138-1-javadoc.jar.sha512' is not valid

The following workaround helps (it renames timestamp-based files to -SNAPSHOT), however, it would be great if the plugin generated the proper archives in the first place

if (project.version.toString().endsWith("-SNAPSHOT")) {
    val snapshotRe = Regex("20[0-9]{6}.[0-9]{6}-[0-9]+")
    tasks.withType<Zip>()
        .matching { it.name.startsWith("zip") && it.name.endsWith("Publication") }
        .configureEach {
            rename {
                it.replace(snapshotRe, "SNAPSHOT")
            }
        }
}

Related environent and versions

No response

Reproduction steps

No response

Anything else?

No response

[martinbonnin]

TIL Central Portal now supports SNAPSHOTs. I thought they were going to deprecate that.
Agreed, we should definitely support them.

[martinbonnin]

Mmm, did it work for you? I'm getting the following error if I just replace the names inside the zip:

> Deployment has failed:
  {"pkg:maven/net.mbonnin.tnmcp/module1@0.0.3-SNAPSHOT":["version cannot be a SNAPSHOT"],"pkg:maven/net.mbonnin.tnmcp/module2@0.0.3-SNAPSHOT":["version cannot be a SNAPSHOT"]}

Looking at https://central.sonatype.org/publish/publish-portal-snapshots/#publishing-with-the-central-publishing-maven-plugin, looks like the SNAPSHOTs, are still using the good old maven publishing process, i.e POST each individual file to https://central.sonatype.com/repository/maven-snapshots/? Or did you find a way to make it work with the central API?

[vlsi]

I guess the snapshots should be explicitly enabled on a namespace in the portal ui. Did you enable them?

[martinbonnin]

Yup, I did but the portal is not happy:

[vlsi]

Right you are. I had extra "missing signatures" warnings, so I missed there were "version cannot be a SNAPSHOT" in my case as well.

On the other side, it looks like Gradle's default publishAllPublicationsToCentralSnapshotsRepository is good enough to publish snapshots:

if (!project.version.toString().endsWith("-SNAPSHOT")) {
    publishing {
        repositories {
            maven {
                name = "centralSnapshots"
                url = uri("https://central.sonatype.com/repository/maven-snapshots")
                credentials(PasswordCredentials::class)
            }
        }
    }
}
// Then publishAllPublicationsToCentralSnapshotsRepository successfully publishes the snapshots

Of course, it would be great if the plugin could automatically use this for the snapshots, however, at least it would be great to raise an error if the user attempts publishing snapshots via nmcp tasks.