gradle-maven-publish-plugin icon indicating copy to clipboard operation
gradle-maven-publish-plugin copied to clipboard

Published 20 hours ago • verified publisher icon vanniktech

GPG 2.3+ format clash

Open steve-the-edwards opened this issue 3 years ago • 1 comments
trafficstars

I am having trouble publishing locally after upgrading GPG past 2.1 on a new computer where I no longer have secring.gpg and I am not sure where to point the plugin to find the secret key in the ~/.gnupg/private-keys-v1.d folder as per the new format. See https://github.com/gpg/gnupg/blob/master/agent/keyformat.txt

Any ideas on options here other than downgrading GPG? How difficult is it to support updated GPG format?

steve-the-edwards avatar Jul 18 '22 20:07 steve-the-edwards

The workaround (very workable) is:

gpg --export-secret-key <YOUR-KEY-ID> > secring.gpg

So not a big concern I realize.

steve-the-edwards avatar Jul 18 '22 20:07 steve-the-edwards

That is the solution I went with as well. The 2 alternatives are in memory keys (mostly meant for CI) and pointing Gradle to a gpg agent https://docs.gradle.org/7.4.2/userguide/signing_plugin.html#sec:using_gpg_agent

Signing is in general handled by Gradle and there is this long standing issue for this https://github.com/gradle/gradle/issues/888

gabrielittner avatar Aug 21 '22 11:08 gabrielittner