commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r864772 - in /websites/staging/commons/trunk/content: ./ releases/prepare.html
Date Fri, 07 Jun 2013 22:45:02 GMT
Author: buildbot
Date: Fri Jun  7 22:45:01 2013
New Revision: 864772

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 Fri Jun  7 22:45:01 2013
@@ -1 +1 @@
-1490855
+1490858

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 Fri Jun  7 22:45:01 2013
@@ -661,6 +661,13 @@
       </p><div><pre>
         mvn deploy -Prelease
       </pre></div>
+      If you want to do a test deployment first, you can add the following option:
+      <div><pre>
+        mvn deploy -Prelease -Ptest-deploy
+      </pre></div>
+      The &quot;test-deploy&quot; profile uploads the artifacts to target/deploy
instead of Nexus so one can check all the required files
+      have been created with the expected contents.
+      Best to run &quot;mvn clean&quot; before doing the live deployment.
       
       <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>



Mime
View raw message