chore(build): Maven Central publishing via vanniktech (Central Portal)#9
Merged
Merged
Conversation
…Portal) Replace the bare maven-publish + hand-rolled publishing block with the vanniktech maven-publish plugin, which targets the new Central Portal: it signs all artifacts, builds the sources + javadoc jars, and uploads the deployment bundle. POM metadata carried over unchanged. Scaffold only: the plugin version is a starting point (verify latest), and the Central Portal token + GPG signing key are read from ~/.gradle/gradle.properties or env, never committed. Coordinates dev.hivens:libtray, version from the git tag.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Wire libtray for publishing to Maven Central (new Central Portal,
central.sonatype.com) so consumers can pin a legible semver
(
dev.hivens:libtray:0.1.0) instead of a raw commit sha.maven-publish+ hand-rolledpublishing {}block withthe vanniktech
com.vanniktech.maven.publishplugin. It appliesmaven-publish + signing, builds the sources + javadoc jars, signs every
artifact, assembles the deployment bundle, and uploads it to the Central
Portal Publisher API. The existing POM metadata carries over unchanged.
SonatypeHost.CENTRAL_PORTAL(the namespace isverified on the new portal; the plugin's no-arg default has varied by
version and could hit legacy OSSRH).
withSourcesJar()/withJavadocJar()-- the pluginmanages those (declaring them twice double-registers the artifacts).
Plugin version pinned in the catalog as a starting point; bump to the
latest before relying on it. Secrets (Central Portal token + GPG signing
key) are read from
~/.gradle/gradle.propertiesor env and are nevercommitted. Version comes from the git tag, so release flow is: tag
0.1.0->./gradlew publishToMavenCentral.Test plan
./gradlew helpconfigures cleanly with the plugin appliedpublishToMavenCentral/publishAndReleaseToMavenCentraltasks registereddev.hivens:libtray:0.1.0to the Central Portal