in the other repos we use `publishToSonatype`, i'm not sure what the differences is between that and `publishMavenPublicationToSonatypeRepository`

[Trask Stalnaker]

          in the other repos we use `publishToSonatype`, i'm not sure what the differences is between that and `publishMavenPublicationToSonatypeRepository`

also we don't seem to need -Pfinal=false in the other repos

Originally posted by @trask in #55 (comment)

[jason plumb]

I'm also not entirely sure, but I suspect it might be a difference between io.github.gradle-nexus.publish-plugin (https://github.com/gradle-nexus/publish-plugin) and maven-publish (https://docs.gradle.org/current/userguide/publishing_maven.html).

It looks like core and instrumentation use both....I don't understand why you'd want or need both...

[César]

I'm also not entirely sure, but I suspect it might be a difference between io.github.gradle-nexus.publish-plugin (https://github.com/gradle-nexus/publish-plugin) and maven-publish (https://docs.gradle.org/current/userguide/publishing_maven.html).

It looks like core and instrumentation use both....I don't understand why you'd want or need both...

That's right they're different but they complement each other, the maven-publish plugin is Gradle's official way to set up and publish maven publications from a project, whereas io.github.gradle-nexus.publish-plugin takes the publications created by maven-publish and uploads them to maven central, automating the whole process of creating sonatype's staging "repo", then closing and releasing it too. The automation of these processes is the value provided by the nexus publish plugin, as they mention in maven central's doc where they talk about a plugin named "Gradle Nexus Staging Plugin" which was later deprecated in favor of the nexus publish plugin.