Author: vmassol
Date: Sat Apr 1 00:25:25 2006
New Revision: 390618
URL: http://svn.apache.org/viewcvs?rev=390618&view=rev
Log:
Doc update
Modified:
maven/plugins/trunk/maven-clover-plugin/src/site/apt/introduction.apt
Modified: maven/plugins/trunk/maven-clover-plugin/src/site/apt/introduction.apt
URL:
http://svn.apache.org/viewcvs/maven/plugins/trunk/maven-clover-plugin/src/site/apt/introduction.apt?rev=390618&r1=390617&r2=390618&view=diff
==============================================================================
--- maven/plugins/trunk/maven-clover-plugin/src/site/apt/introduction.apt
(original)
+++ maven/plugins/trunk/maven-clover-plugin/src/site/apt/introduction.apt Sat
Apr 1 00:25:25 2006
@@ -4,7 +4,7 @@
Vincent Massol
<[EMAIL PROTECTED]>
------
- March 23, 2006
+ April 1st, 2006
Introduction
@@ -24,9 +24,10 @@
* Instrumenting Java sources with Clover so that they generate coverage logs
to a {{{http://cenqua.com/clover/doc/adv/database.html}Clover database}}
when they are exercised.
- * Generating a report from a
{{{http://cenqua.com/clover/doc/adv/database.html}Clover database}}. Note that
- if you execute the Clover plugin in a multimodule build it will
automatically generate individual reports
- for each module but also a master report aggregating all module reports.
+ * Aggregating Clover databases found in children modules into a single
database so that reporting and checking
+ for test coverage can be done at the level of the full project.
+
+ * Generating a report from a
{{{http://cenqua.com/clover/doc/adv/database.html}Clover database}}.
* Verifying that your source code has a defined test coverage percentage
and fail the build if it's
below that level. This is the equivalent of the
