Publish to Maven Central?

[martinbonnin]

Hi 👋

It doesn't look like this plugin is published to Maven Central? Would you consider doing so?

Dealing with extra repos always adds a bit of friction in my builds.

[YongGoose]

I’ve only published it to the Gradle Plugin Portal, not to Maven Central.

• https://plugins.gradle.org/u/YongGoose

Is there any particular reason why it should also be published to Maven Central?
If it’s considered necessary, I’m planning to publish it to Maven Central too.

[martinbonnin]

The main reason from a consumer perspective is ease of use (only a single repo to monitor).

From a producer perspective, there are a bunch of other reasons outlined in gradle/plugin-portal-requests#225

[YongGoose]

The main reason from a consumer perspective is ease of use (only a single repo to monitor).

From a producer perspective, there are a bunch of other reasons outlined in gradle/plugin-portal-requests#225

Seems reasonable :)
@oleg-nenashev WDYT?

[martinbonnin]

Also sounds like a great dogfooding opportunity!

[oleg-nenashev]

I am +1 for publishing

[oleg-nenashev]

Bonus points for automating releases to Maven Cwentral so that they can be triggered from GitHub Actions our by cutting a new release. Example of my release pipeline: https://github.com/wiremock/wiremock-testcontainers-java/blob/main/.github/workflows/release.yml