svn commit: r607296 - in /maven/enforcer/trunk/maven-enforcer-plugin/src/site: apt/index.apt apt/usage.apt fml/faq.fml

[de...@apache.org]

Author: dennisl
Date: Fri Dec 28 09:30:57 2007
New Revision: 607296

URL: http://svn.apache.org/viewvc?rev=607296&view=rev
Log:
o Minor tweaks to the documentation.

Modified:
    maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/index.apt
    maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/usage.apt
    maven/enforcer/trunk/maven-enforcer-plugin/src/site/fml/faq.fml

Modified: maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/index.apt?rev=607296&r1=607295&r2=607296&view=diff
==============================================================================
--- maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/index.apt (original)
+++ maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/index.apt Fri Dec 28 09:30:57 2007
@@ -25,11 +25,11 @@
 
 Maven Enforcer Plugin - The Loving Iron Fist of Maven\x99
 
-	The Enforcer plugin provides goals to control certain environmental constraints such as Maven Version, JDK version, and OS family.
+  The Enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family.
 
 * Goals Overview
 
-  The Enforcer plugin has two goals:
+  The Enforcer plugin has three goals:
 
   *{{{enforce-mojo.html}enforcer:enforce}} executes rules for each project in a multi-project build.
   

Modified: maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/usage.apt
URL: http://svn.apache.org/viewvc/maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/usage.apt?rev=607296&r1=607295&r2=607296&view=diff
==============================================================================
--- maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/usage.apt (original)
+++ maven/enforcer/trunk/maven-enforcer-plugin/src/site/apt/usage.apt Fri Dec 28 09:30:57 2007
@@ -45,11 +45,11 @@
    <<<pom.xml>>>. The enforcers execute the configured rules to check for certain constraints. 
    The available standard rules are described {{{rules/index.html}here}}. Besides the rules to execute, these goals support three options:
    
-   * {{{enforce-mojo.html#skip}skip}} - a quick way to skip checks via a profile or using -Denforcer.skip=true from the command line.
+   * {{{enforce-mojo.html#skip}skip}} - a quick way to skip checks via a profile or using <<<-Denforcer.skip=true>>> from the command line.
    
-   * {{{enforce-mojo.html#fail}fail}} - if the goal should fail the build when a rule fails. The default is true. If false, the errors will be logged as warnings.
+   * {{{enforce-mojo.html#fail}fail}} - if the goal should fail the build when a rule fails. The default is <<<true>>>. If false, the errors will be logged as warnings.
    
-   * {{{enforce-mojo.html#failFast}failFast}} - if the goal should stop checking after the first failure. The default is false.
+   * {{{enforce-mojo.html#failFast}failFast}} - if the goal should stop checking after the first failure. The default is <<<false>>>.
    
    []
    

Modified: maven/enforcer/trunk/maven-enforcer-plugin/src/site/fml/faq.fml
URL: http://svn.apache.org/viewvc/maven/enforcer/trunk/maven-enforcer-plugin/src/site/fml/faq.fml?rev=607296&r1=607295&r2=607296&view=diff
==============================================================================
--- maven/enforcer/trunk/maven-enforcer-plugin/src/site/fml/faq.fml (original)
+++ maven/enforcer/trunk/maven-enforcer-plugin/src/site/fml/faq.fml Fri Dec 28 09:30:57 2007
@@ -19,17 +19,17 @@
  *
 -->
 <faqs id="FAQ" title="Frequently Asked Questions">
- <part id="General">
-   <faq id="question">
-     <question>Why can't I just use the prerequisites tag in the pom?</question>
-     <answer>
+  <part id="General">
+    <faq id="question">
+      <question>Why can't I just use the prerequisites tag in the pom?</question>
+      <answer>
         <p>
-            The prerequisites tag was designed to be used by tools like plugins. It will work for regular projects, but it isn't
-            inherited to their children. If it is set in a parent reactor, then Maven will do the check. However if one of the
-            children are built, the check is not performed. The enforcer plugin is designed to allow centralized control over the build environment from 
-            a single "super-pom", and to allow greater flexibility in version specification by supporting ranges.
+          The prerequisites tag was designed to be used by tools like plugins. It will work for regular projects, but it isn't
+          inherited to their children. If it is set in a parent reactor, then Maven will do the check. However if one of the
+          children are built, the check is not performed. The enforcer plugin is designed to allow centralized control over the build environment from 
+          a single "super-pom", and to allow greater flexibility in version specification by supporting ranges.
         </p>
-     </answer>
-      </faq>
- </part>
+      </answer>
+    </faq>
+  </part>
 </faqs>