svn commit: r883933 - in /websites/staging/isis/trunk: cgi-bin/ content/ content/contributors/verifying-releases.html

[bu...@apache.org]

Author: buildbot
Date: Thu Oct 24 12:38:49 2013
New Revision: 883933

Log:
Staging update by buildbot for isis

Modified:
    websites/staging/isis/trunk/cgi-bin/   (props changed)
    websites/staging/isis/trunk/content/   (props changed)
    websites/staging/isis/trunk/content/contributors/verifying-releases.html

Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Oct 24 12:38:49 2013
@@ -1 +1 @@
-1534741
+1535356

Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Oct 24 12:38:49 2013
@@ -1 +1 @@
-1534741
+1535356

Modified: websites/staging/isis/trunk/content/contributors/verifying-releases.html
==============================================================================
--- websites/staging/isis/trunk/content/contributors/verifying-releases.html (original)
+++ websites/staging/isis/trunk/content/contributors/verifying-releases.html Thu Oct 24 12:38:49 2013
@@ -315,20 +315,24 @@ gpg --verify isis-x.y.z.zip.asc isis-x.y
 rm -rf ~/.m2/repository/org/apache/isis
 </pre>
 
-<p>The build process depends on whether the artifact is of Isis core or of one of its components:</p>
+<p>The build process depends on whether the artifact is of Isis core or of one of its components.</p>
 
-<ul>
-<li>For Isis core, build using the <code>-o</code> offline flag:</p>
+<p><strong>For Isis core</strong>, first download any dependencies:</p>
+
+<p><code>mvn dependency:go-offline</code></p>
+
+<p>Check that no Isis artifacts have yet been downloaded, ie there is no <code>~/.m2/org/repository/org/apache/isis</code> directory.  If there are, it could indicate that the release being verified incorrectly references previous versions of Isis core.
+Assuming all is ok, build using the <code>-o</code> offline flag:</p>
 
 <p><code>mvn clean install -o</code></p>
 
-<p>Confirm that the versions of the Isis artifacts now cached in your local repository are correct.</li>
-<li>For an Isis component, build without the offline flag; Maven should pull down the component's dependencies from the Maven central repo:</p>
+<p>Confirm that the versions of the Isis artifacts now cached in your local repository are correct.</p>
+
+<p><strong>For an Isis component</strong>, build without the offline flag; Maven should pull down the component's dependencies from the Maven central repo:</p>
 
 <p><code>mvn clean install</code></p>
 
-<p>Confirm that the versions of the Isis artifacts now cached in your local repository are correct (both those pulled down from Maven central repo, as well as those of the component built locally).</li>
-</ul>
+<p>Confirm that the versions of the Isis artifacts now cached in your local repository are correct (both those pulled down from Maven central repo, as well as those of the component built locally).</p>
 
 <p>The above steps are the bare minimum you should perform before casting a vote.  Ideally, you should also run an Isis application (eg one of the examples) against the new code (either against a new version of core, or configured to use the new version of the component).</p>