Skip to content

Configure publish plugin. - #26

Merged
damon140 merged 1 commit into
mainfrom
gradle-maven-publish-plugin
Aug 20, 2026
Merged

damon140 merged 1 commit into
mainfrom
gradle-maven-publish-plugin

Conversation

@damon140

@damon140 damon140 commented Aug 10, 2026 •

Copy link
Copy Markdown
Collaborator

Configures a Maven Central publishing plugin.

Adds two authors.

Not using the Gradle maven-publish plugin as it does not support publishing to Maven Central completely in 2026, although it did used to.

Uses plugin com.vanniktech.maven.publish instead. Note this plugin mandates the use of "short" PGP key ids, and not the preferred more modern "long" format. This appears to require the generation step for secring.gpg to be done with the matching key id length.

Some command line notes about secring.gpg creation:

# list secret keys used for signing so we can get the key ids
gpg --list-secret-keys --keyid-format=long

# Find long fingerprint in output of above, from the `sec` key, then take the rightmost 8 characters as the "short" key id to use below

gpg --export-secret-keys -o secring.gpg <key-id-goes-here>

@damon140
damon140 requested a review from dustmachine August 10, 2026 07:20

@dustmachine dustmachine left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, this looks like it works

@damon140
damon140 merged commit ae4d515 into main Aug 20, 2026
1 check passed
@damon140
damon140 deleted the gradle-maven-publish-plugin branch August 20, 2026 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants