From 473b019ca81f9a8ffda4ab21ddb27a87e43cbe1e Mon Sep 17 00:00:00 2001
From: Emmanuel Venisse <evenisse@apache.org>
Date: Thu, 30 Jun 2005 16:04:12 +0000
Subject: [PATCH] [MNG-543]. Small patch for General FAQ and Plugin Overview.

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@208644 13f79535-47bb-0310-9956-ffa450edef68
---
 maven-site/src/site/fml/general.fml                 | 13 +++++++++++++
 .../src/site/xdoc/developers/plugin-overview.xml    | 13 +++++++++++--
 2 files changed, 24 insertions(+), 2 deletions(-)

diff --git a/maven-site/src/site/fml/general.fml b/maven-site/src/site/fml/general.fml
index 9b16d9d4c0..1badd5a31b 100644
--- a/maven-site/src/site/fml/general.fml
+++ b/maven-site/src/site/fml/general.fml
@@ -16,5 +16,18 @@
         </p>
       </answer>
     </faq>
+    <faq id="available-plugins">
+      <question>How do I list available plugins?</question>
+      <answer>
+        <p>
+		  To see a list of available plugins, browse the Maven 2 plugin repository
+		  at <a href="http://www.ibiblio.org/maven2/plugins/">http://www.ibiblio.org/maven2/plugins/</a>.  
+		  Plugins are organized according to a directory structure that resembles
+		  the standard Java package naming convention.  To see a list of available
+		  plugins from the Maven project look in the <a href="http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/">org/apache/maven subfolder</a>
+		  of this directory.
+        </p>
+      </answer>
+    </faq>
   </part>
 </faqs>
diff --git a/maven-site/src/site/xdoc/developers/plugin-overview.xml b/maven-site/src/site/xdoc/developers/plugin-overview.xml
index 59892e87af..664db71baf 100644
--- a/maven-site/src/site/xdoc/developers/plugin-overview.xml
+++ b/maven-site/src/site/xdoc/developers/plugin-overview.xml
@@ -97,8 +97,15 @@
     </section>
     <section name="Definitions">
       <subsection name="What is a Plugin?">
+        Maven is a framework for the execution of plugin goals.  Every action you 
+        take in Maven is really just calling out to an existing maven plugin. 
+        When you compile, clean, create a JAR, generate a site, or execute
+        unit tests, Maven is executing goals from the appropriate plugins. 
       </subsection>
       <subsection name="What is a Mojo (And Why the H--- is it Named 'Mojo')?">
+        MOJO is a play on POJO (Plain-old-Java-object), substituting "Maven" for
+        "Plain".  A Mojo is really just a goal in Maven 2, and plug-ins consist of 
+        any number of goals (Mojos). 
       </subsection>
       <subsection name="What is the Build Lifecycle?">
       </subsection>
@@ -131,8 +138,10 @@
     <section name="Resources">
       <ul>
         <li>
-          <a href="../plugin-management.html">Managing plugin configuration in 
-            large projects</a>
+          <a href="developing-plugins-with-marmalade.html">Developing Plugins with Marmalade</a>
+        </li>
+        <li>
+          <a href="mojo-api-specification.html">MOJO API Specification</a>
         </li>
       </ul>
     </section>