You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by br...@apache.org on 2006/10/19 04:31:01 UTC

svn commit: r465449 - /maven/plugins/trunk/maven-pmd-plugin/src/site/apt/examples/violationChecking.apt

Author: brianf
Date: Wed Oct 18 19:31:00 2006
New Revision: 465449

URL: http://svn.apache.org/viewvc?view=rev&rev=465449
Log:
MPMD-43 : updated site info

Modified:
    maven/plugins/trunk/maven-pmd-plugin/src/site/apt/examples/violationChecking.apt

Modified: maven/plugins/trunk/maven-pmd-plugin/src/site/apt/examples/violationChecking.apt
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-pmd-plugin/src/site/apt/examples/violationChecking.apt?view=diff&rev=465449&r1=465448&r2=465449
==============================================================================
--- maven/plugins/trunk/maven-pmd-plugin/src/site/apt/examples/violationChecking.apt (original)
+++ maven/plugins/trunk/maven-pmd-plugin/src/site/apt/examples/violationChecking.apt Wed Oct 18 19:31:00 2006
@@ -25,6 +25,8 @@
 
   The pmd:check and pmd:cpd-check goals allow you to configure your build to fail if any errors are found in the PMD or
   CPD reports respectively and, in doing so, enforce your own custom code quality rules.
+  
+  The rule violations may optionally be displayed on the build output using the verbose setting.
 
   The following code fragment enables both the standard PMD check and the CPD check in a build, during the <<<verify>>>
   phase.