Publish to Maven Central

[eriwen]

Context

We should resolve this library from Maven Central so consumers do not have to access repo.gradle.org. This will be faster and more stable.

@marcphilipp has recommended that we use the group org.gradle.exemplar. I agree.

[marcphilipp]

Using the io.github.gradle-nexus.publish-plugin would allow automating dealing with Sonatype's OSSRH Nexus.

[britter]

I think if we move to a new groupId we should also align the rest of the naming in this project. The status quo is:

repository name	exemplar
subprojects	sample-check and sample-discovery
root package	`org.gradle.samples`
GAV	`org.gradle:sample-check:0.12.6`

My proposal:

repository name	exemplar
subprojects	check and discovery
root package	`org.gradle.exemplar`
GAV	`org.gradle.exemplar:check:0.12.6` & `org.gradle.exemplar:discovery:0.12.6`

[big-guy]

Does GE use exemplar or sample-check?

[britter]

Yes, we're using it to test the Test Distribution Gradle plugin manual.

[big-guy]

this LGTM

[eriwen]

Also LGTM

[pbielicki]

TODO:

• Add project to the TeamCity
• Add all required env variables to it (e.g. for publishing to Maven Central signing the artifacts)