You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by bu...@apache.org on 2013/06/08 00:45:02 UTC
svn commit: r864772 - in /websites/staging/commons/trunk/content: ./
releases/prepare.html
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 "test-deploy" 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 "mvn clean" 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>