Add support for custom repository & usage outside "Wiremock team workflow"

[pinguet62]

Proposal

Hello 🖖

I would like create my own extension, and publish it for community 💪

But it's not easy (because of shadow & Gradle configuration):

1. I tried the wiremock-extension-template GitHub template
   Ok for base configuration and local packaging.
   But publish to Maven Centrale is complicated.
2. I tried your gradle-wiremock-extension-plugins (yes, before release of Update to use gradle-wiremock-extension-plugins. wiremock-extension-template#8):
   Gradle configuration is very nice (1 line) 👌
   But when I tried to publish to Maven Central, I see many "hard coded" configuration (group.id, GitHub user base repository, ...)
   

For developers section, the configuration is possible:

In order to allow usage of plugin to any contributor, could you add more configuration for personal projects?

References

No response

[tomasbjerre]

I also need to adjust it a bit. I need to turn off Shadow. Created a PR with a proposal:
#20

I started fiddling with this in my personal projects and I think I'll have 3 different plugins:

• The release process: https://github.com/tomasbjerre/conventional-release-gradle-plugin
• The Code style and analysis: https://github.com/tomasbjerre/java-convention-gradle-plugin
• Dependency updating: https://github.com/tomasbjerre/update-versions-gradle-plugin

Perhaps it is a good idea to split this plugin into 2 plugins. One with the release process, only for projects in the WireMock organization. One with the other stuff that can be re-used outside of the organization.

[oleg-nenashev]

+1 for making the things more generic, in terms of options. I would prefer to keep the original options as is to have a kind of sustainable hosting of plugins in this org, but it would be good to allow using the convention for externally maintained plugins