Author: bodewig Date: Sat Apr 6 16:49:01 2013 New Revision: 1465272 URL: http://svn.apache.org/r1465272 Log: gpg plugin may fail when the passphrase has to be specified interactively
Modified: commons/cms-site/trunk/content/xdoc/releases/prepare.xml Modified: commons/cms-site/trunk/content/xdoc/releases/prepare.xml URL: http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/releases/prepare.xml?rev=1465272&r1=1465271&r2=1465272&view=diff ============================================================================== --- commons/cms-site/trunk/content/xdoc/releases/prepare.xml (original) +++ commons/cms-site/trunk/content/xdoc/releases/prepare.xml Sat Apr 6 16:49:01 2013 @@ -501,6 +501,9 @@ </p> <p>This will PGP-sign all artifacts and upload them to a new staging repository, Nexus itself will create MD5 and SHA1 checksums for all files that have been uploaded.</p> + <p>A known problem is that gpg signing may fail if the gpg plugin tries to read the passphrase interactively. + It works if you specify the passphrase when invoking mvn (<code>-Dgpg.passprase=***</code>) or run + <code>gpg-agent</code> before starting mvn.</p> <p>Unfortunately this uploads more than should be part of the Maven repository, in particular the binary and source distribution <code>.tar.gz</code> and <code>.zip</code> files are there as well. Before you <a href="http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage">close</a> the staging