svn commit: r969090 - in /websites/staging/oodt/trunk/content: ./ development.html

[bu...@apache.org]

Author: buildbot
Date: Thu Oct 15 23:14:17 2015
New Revision: 969090

Log:
Staging update by buildbot for oodt

Modified:
    websites/staging/oodt/trunk/content/   (props changed)
    websites/staging/oodt/trunk/content/development.html

Propchange: websites/staging/oodt/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Oct 15 23:14:17 2015
@@ -1 +1 @@
-1708851
+1708903

Modified: websites/staging/oodt/trunk/content/development.html
==============================================================================
--- websites/staging/oodt/trunk/content/development.html (original)
+++ websites/staging/oodt/trunk/content/development.html Thu Oct 15 23:14:17 2015
@@ -151,8 +151,14 @@ h2:hover > .headerlink, h3:hover > .head
             </p>
             <p>Those with access to the Apache Jenkins instance can view our 
             <a href="https://builds.apache.org/job/oodt-coverage/ws/target/site/clover/dashboard.html">Clover Test Coverage Reports</a>.
-            You can generate the Clover reports yourself if you execute <code>mvn clover2:setup test clover2:aggregate clover2:clover
--Dmaven.test.failure.ignore=true</code></p>
+            You can generate the Clover reports yourself if you execute:</p>
+            <code>mvn clean com.atlassian.maven.plugins:maven-clover2-plugin:instrument
+com.atlassian.maven.plugins:maven-clover2-plugin:setup
+com.atlassian.maven.plugins:maven-clover2-plugin:aggregate
+com.atlassian.maven.plugins:maven-clover2-plugin:clover test install
+-Dmaven.clover.skipGroverJar=true</code></p>
+            <p>To find out more about Clover Tests please visit the <a href="find out more about Clover visit:
+https://confluence.atlassian.com/display/CLOVER/Clover-for-Maven+2+and+3+User's+Guide">Clover wiki page</a>.</p>
             <h4 id="roadmap">OODT Roadmap</h4>
             <p>
               Using the issue tracker we try our best to plan our releases setting issues for releases