svn commit: r857521 - in /websites/staging/commons/trunk/content: ./ releases/prepare.html

[bu...@apache.org]

Author: buildbot
Date: Sat Apr  6 16:49:14 2013
New Revision: 857521

Log:
Staging update by buildbot for commons

Modified:
    websites/staging/commons/trunk/content/   (props changed)
    websites/staging/commons/trunk/content/releases/prepare.html

Propchange: websites/staging/commons/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Apr  6 16:49:14 2013
@@ -1 +1 @@
-1465232
+1465272

Modified: websites/staging/commons/trunk/content/releases/prepare.html
==============================================================================
--- websites/staging/commons/trunk/content/releases/prepare.html (original)
+++ websites/staging/commons/trunk/content/releases/prepare.html Sat Apr  6 16:49:14 2013
@@ -643,6 +643,9 @@
       
       <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 (<tt>-Dgpg.passprase=***</tt>) or run
+        <tt>gpg-agent</tt> before starting mvn.</p>
       <p>Unfortunately this uploads more than should be part of the Maven repository, in particular the binary and source
         distribution <tt>.tar.gz</tt> and <tt>.zip</tt> files are there as well.  Before you
         <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage">close</a> the staging