merging in changes from the xdoc version, before I delete the xdoc version.

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@209620 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
John Dennis Casey 2005-07-07 17:40:03 +00:00
parent e2468df6f4
commit b39c286733
2 changed files with 23 additions and 5 deletions

View File

@ -53,8 +53,8 @@ Developing Maven 2.0 Plugins
* Resources * Resources
[[1]] {{{../plugin-management.html}Managing plugin configuration in large [[1]] {{{developers/developing-plugins-with-marmalade.html}Developing plugins
projects}} with Marmalade}}
[[2]] {{{../plugin-configuration.html}Configuring plugins}} [[2]] {{{developers/mojo-api-specification.html}Mojo API specification}}

View File

@ -109,7 +109,25 @@ Plugin Overview
** What is a Plugin? ** 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.
** What is a Mojo (<And Why the H--- is it Named 'Mojo'>)? ** 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).
** What is the Build Lifecycle? (Overview) ** What is the Build Lifecycle? (Overview)
* Resources
[[1]] {{{developers/plugin-development-guide.html}Plugin development guide}}
[[2]] {{{plugin-management.html}Managing plugin configuration in large
projects}}
[[3]] {{{plugin-configuration.html}Configuring plugins}}