Publish the Gradle plugin to Maven Central?

[martinbonnin]

Hi 👋

Would you consider publishing the Gradle Plugin to Maven Central? The runtime is already there so using the plugin requires Maven Central anyways.

[qurbonzoda]

Hi!
Could you please clarify what benefits publishing the plugin to Maven Central would have in your use case?

[martinbonnin]

From the top of my head:

Advantages for me:

• Artifacts are immutable on Maven Central
• Maven Central hosts everything themselves. Gradle Portal proxies Jcenter and/or Maven Central so I never know where an artifact is coming from.
• There've been occasions where pom files are different between MavenCentral and Gradle Portal.
• Historically, I've found MavenCentral to have less outages (certainly because Gradle Portal is prone to Jcenter failures)
• Anecdotally, it simplifies my build configuration because I can rely on a single repository

Advantages for you:

• You get download stats
• You can share the publishing configuration with the runtime
• You don't pull a closed source plugin in your build
• MavenCentral has organization support, you can share an account with several members, you don't have to share email/password

Disadvantages for you and me:

• The plugin is less discoverable

[JakeWharton]

The plugin is less discoverable

You can still publish to Gradle's bespoke plugin repository and to Maven Central