On Oct 29, 2010, at 3:59 PM, Les Hazlewood wrote: > It appears I'll have the 2nd-attempt release to vote upon in the next > 20 minutes. I had a _hell_ of a time trying to get the gpg signing to > work: Even though I set a <gpg.passphrase> in my ~/.m2/settings.xml > file, the build froze and wouldn't move past the point where it looked > up my key. > > I finally got around the issue by starting the gpg-agent and having to > write some bash scripts to start it up based on this: > > http://www.linuxquestions.org/questions/linux-security-4/gpg-gpg-agent-cant-connect-to-root-gnupg-s-gpg-agent-611843/ > > Now when I run the build, a screen will prompt me for the gpg > password, and I enter it in and it works. > > Does anyone know why I am prompted for a password even though I have > the <gpg.passphrase> value set in ~/.m2/settings.xml?
Putting your gpg passphrase in settings.xml is a poor practice, imho. When I release I always type in my password. Regards, Alan
