My POM is set up exactly as desired by Sonatype for releasing to their OSSRH
repository, described in
http://nexus.sonatype.org/oss-repository-hosting.html
except that I'm using version 2.0 of the release plugin and 1.0 of the gpg
plugin.
I don't get prompted for my signing passphrase when doing a release:perform. If
I do the gpg:sign manually, I get prompted.
I'm currently using the workaround of entering
-Dgpg.passphrase=foo -Darguments="-Dgpg.passphrase=foo"
on the command line. Since I'm doing this on a Mac laptop and I wipe the
.bash_history file afterwards, I'm not too worried about my passphrase being
sniffed, but it's ugly.
So, (a) is there a fix, or (b) does someone know how to get the gpg agent
working with this on a Mac. It seems to work with git commits to GitHub from
terminal, but doesn't get activated when I add
<useAgent>true</useAgent>
to the <configuration> element of the gpg plugin. It just hangs, same as if I
don't put the passphrase on the command line.
Any assistance would be appreciated, or an ETA on when the basic bug will be
fixed. (I actually would prefer to get the agent working.)
BTW, I'm running version 2.0.12 of the gpg-agent on Mac OS X 10.6.2.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
