"org.wiremock" on Maven Central - Policy and Automation

[oleg-nenashev]

Proposal

We would like to Mover WireMock core, extensions and other Java tools to a single location under org.wiremock on Maven Central. It would require some policies and automation so that all maintainers of components could publish there.

Structure

• org.wiremock as a root. Core components like wiremock or wiremock-standalone will be under this root
  • org.wiremock.extensions - groupID for extensions
  • org.wiremock.tools - groupID for any associated developer tools (e.g. Maven plugins)
  • org.wiremock.integrations.{type} - groupID for integration libraries
  • {type}- A subgroup defining type of the integration, for example testcontainers, springboot or kotlin

Acceptance criteria

• [x] Define structure of the org.wiremock group and subgroups
• [x] Create Automation
• [x] Move test components to the new engine: WireMock 3 Beta, WireMock TestContainers module, some extensions
• [x] Setup Automation to help with publishing of releases from the wiremock GitHub org. These could be either GitHub Actions or some mirroring of GitHub Packages
• [x] Document releasing extensions in the extension developer guide

References

• Docs: https://github.com/wiremock/community/blob/main/infra/maven-central.md
• https://github.com/wiremock/wiremock/issues/2237
• https://github.com/wiremock/wiremock-testcontainers-java/issues/56
• https://github.com/wiremock/wiremock-state-extension/issues/71

Follow-ups:

• https://github.com/wiremock/ecosystem/issues/19
• Same for Maven?

[oleg-nenashev]

Gradle Convention Plugin PoC: https://github.com/wiremock/gradle-wiremock-extension-plugins/pull/1

[kyle-winkelman]

I am noticing wiremock-grpc-extension, wiremock-webhooks-extension, and their -standalone versions being placed in org.wiremock rather than org.wiremock.extensions. Do we need to create issues in those respective repos to get this fixed?

[oleg-nenashev]

I talked to @tomakehurst as a maintainer, and indeed we are going to fix it. The problem is that the fix will not apply to the historical artifacts, so I guess those ones will stay there forever for old versions

[oleg-nenashev]

I mostly completed it before changing the job, hence closing