Closed bpsm closed 4 years ago
@bpsm https://kemitix.github.io/2018/02/24/gpg-signing-failed.html does not fix the issue?
Thanks.
I'd found something similar yesterday,but it was without --batch
. I tried adding --batch
myself after grovelling through the gpg man page, but it didn't seem to help. I'll give it another shot with a fresh release. (probably 0.7.1)
I was able to get deploy to oss.sonatype.org to work as follows:
mvn release:prepare -Pgpg
activates the gpg profile from my settings.xml which sets gpg.passphrase. Previously I'd not been able to get release:perform to work reliably and had given up on it and was doing releases by hand, followed by explicit calls to gpg:sign-and-deploy-file.mvn release:perform -Pgpg
works, taking the credentials necessary to upload to oss.sonatype.org form my settings.xmlI've released and published 0.7.1. It is not (as I write this) yet visible on Maven central, but I imagine it will appear there within the next 24 hours or so.
Whatever magic set of configurations I made years ago to allow releases to Maven Central via Sonatype has ceased functioning for reasons I have not yet been able to diagnose. As a result 0.7.0 has been tagged, but not published on Maven Central.
I've googled around for what to do about "No pinetry" but not yet found anything that leads me to solution.