Author: dennisl
Date: Thu Nov  2 16:08:33 2006
New Revision: 470612

URL: http://svn.apache.org/viewvc?view=rev&rev=470612
Log:
[MNG-1290] What is a Mojo?

o Added explanations to /glossary.html and 
/developers/mojo-api-specifications.html.

Modified:
    maven/site/trunk/src/site/apt/glossary.apt
    maven/site/trunk/src/site/xdoc/developers/mojo-api-specification.xml

Modified: maven/site/trunk/src/site/apt/glossary.apt
URL: 
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/glossary.apt?view=diff&rev=470612&r1=470611&r2=470612
==============================================================================
--- maven/site/trunk/src/site/apt/glossary.apt (original)
+++ maven/site/trunk/src/site/apt/glossary.apt Thu Nov  2 16:08:33 2006
@@ -43,6 +43,11 @@
     Examples of plugins are: jar, eclipse, war. Plugins are primarily written 
in Java, but Maven
     also supports writing plug-ins in Beanshell and Ant Scripting.
 
+  * {<<Mojo>>}:
+    A plugin written in Java consists of one or more mojos. A mojo is a Java 
class that implements
+    the org.apache.maven.plugin.Mojo interface. This means that a mojo is the 
implementation for
+    a goal in a plugin.
+
 ~~  * {<<Goal>>}: and phases
 ~~    Goals are what are executed to perform an action on the project. For 
example, the
 ~~    <<<jar:jar>>> will compile the current project and produce a JAR.

Modified: maven/site/trunk/src/site/xdoc/developers/mojo-api-specification.xml
URL: 
http://svn.apache.org/viewvc/maven/site/trunk/src/site/xdoc/developers/mojo-api-specification.xml?view=diff&rev=470612&r1=470611&r2=470612
==============================================================================
--- maven/site/trunk/src/site/xdoc/developers/mojo-api-specification.xml 
(original)
+++ maven/site/trunk/src/site/xdoc/developers/mojo-api-specification.xml Thu 
Nov  2 16:08:33 2006
@@ -25,7 +25,9 @@
   <body>
     <section name="Introduction">
       <p>Starting with Maven 2.0, plugins can be written in Java or any of a
-        number of scripting languages. Additionally, Maven tries to stay out of
+        number of scripting languages. Plugins consists of one or more Mojos,
+        each one being the implementation for one of the plugin's goals.
+        Maven tries to stay out of
         the way of the programmer with its new Mojo API. This opens up the
         opportunity for many Mojos to be reused outside of Maven, or bridged
         into Maven from external systems like Ant.</p>


Reply via email to