Author: buildbot
Date: Fri Aug 2 13:20:59 2013
New Revision: 872460
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/guides/introduction/introduction-to-the-lifecycle.html
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Aug 2 13:20:59 2013
@@ -1 +1 @@
-1509673
+1509687
Modified:
websites/staging/maven/trunk/content/guides/introduction/introduction-to-the-lifecycle.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/introduction/introduction-to-the-lifecycle.html
(original)
+++
websites/staging/maven/trunk/content/guides/introduction/introduction-to-the-lifecycle.html
Fri Aug 2 13:20:59 2013
@@ -282,9 +282,9 @@
<p>This command will traverse into all of the subprojects and run
<tt>clean</tt>, then <tt>install</tt> (including all of the prior steps).</p>
<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div>
<div class="section">
-<h4><a name="A_Build_Phase_is_Made_Up_of_Goals">A Build Phase is Made Up of
Goals</a></h4>
-<p>However, even though a build phase is responsible for a specific step in
the build lifecycle, the manner in which it carries out those responsibilities
may vary. And this is done by declaring the goals bound to those build
phases.</p>
-<p>A goal represents a specific task (finer than a build phase) which
contributes to the building and managing of a project. It may be bound to zero
or more build phases. A goal not bound to any build phase could be executed
outside of the build lifecycle by direct invocation. The order of execution
depends on the order in which the goal(s) and the build phase(s) are invoked.
For example, consider the command below. The <tt>clean</tt> and
<tt>package</tt> arguments are build phases while the
<tt>dependency:copy-dependencies</tt> is a goal.</p>
+<h4><a name="A_Build_Phase_is_Made_Up_of_Plugin_Goals">A Build Phase is Made
Up of Plugin Goals</a></h4>
+<p>However, even though a build phase is responsible for a specific step in
the build lifecycle, the manner in which it carries out those responsibilities
may vary. And this is done by declaring the plugin goals bound to those build
phases.</p>
+<p>A plugin goal represents a specific task (finer than a build phase) which
contributes to the building and managing of a project. It may be bound to zero
or more build phases. A goal not bound to any build phase could be executed
outside of the build lifecycle by direct invocation. The order of execution
depends on the order in which the goal(s) and the build phase(s) are invoked.
For example, consider the command below. The <tt>clean</tt> and
<tt>package</tt> arguments are build phases, while the
<tt>dependency:copy-dependencies</tt> is a goal (of a plugin).</p>
<div>
<pre>mvn clean dependency:copy-dependencies package</pre></div>
<p>If this were to be executed, the <tt>clean</tt> phase will be executed
first (meaning it will run all preceeding phases of the clean lifecycle, plus
the <tt>clean</tt> phase itself), and then the
<tt>dependency:copy-dependencies</tt> goal, before finally executing the
<tt>package</tt> phase (and all its preceeding build phases of the default
lifecycle).</p>
@@ -328,7 +328,7 @@
<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div>
<div class="section">
<h4><a name="Plugins">Plugins</a></h4>
-<p>The second way to add goals to phases is to configure plugins in your
project. Plugins are artifacts that provide goals to Maven. Furthermore, a
plugin may have one or more goals wherein each goal represents a capability of
that plugin. For example, the Compiler plugin has two goals: <tt>compile</tt>
and <tt>testCompile</tt>. The former compiles the source code of your main
code, while the later compiles the source code of your test code.</p>
+<p>The second way to add goals to phases is to configure plugins in your
project. Plugins are artifacts that provide goals to Maven. Furthermore, a
plugin may have one or more goals wherein each goal represents a capability of
that plugin. For example, the Compiler plugin has two goals: <tt>compile</tt>
and <tt>testCompile</tt>. The former compiles the source code of your main
code, while the latter compiles the source code of your test code.</p>
<p>As you will see in the later sections, plugins can contain information that
indicates which lifecycle phase to bind a goal to. Note that adding the plugin
on its own is not enough information - you must also specify the goals you want
to run as part of your build.</p>
<p>The goals that are configured will be added to the goals already bound to
the lifecycle from the packaging selected. If more than one goal is bound to a
particular phase, the order used is that those from the packaging are executed
first, followed by those configured in the POM. Note that you can use the
<tt><executions></tt> element to gain more control over the order of
particular goals.</p>
<p>For example, the Modello plugin binds by default its goal
<tt>modello:java</tt> to the <tt>generate-sources</tt> phase (Note: The
<tt>modello:java</tt> goal generates Java source codes). So to use the Modello
plugin and have it generate sources from a model and incorporate that into the
build, you would add the following to your POM in the <tt><plugins></tt>
section of <tt><build></tt>:</p>
@@ -475,7 +475,7 @@
<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div>
<div class="section">
<h3><a name="Built-in_Lifecycle_Bindings">Built-in Lifecycle Bindings</a></h3>
-<p>Some phases have goals binded to them by default. And for the default
lifecycle, these bindings depend on the packaging value. Here are some of the
goal-to-build-phase bindings.</p>
+<p>Some phases have goals bound to them by default. And for the default
lifecycle, these bindings depend on the packaging value. Here are some of the
goal-to-build-phase bindings.</p>
<div class="section">
<h4>Clean Lifecycle Bindings<a name="Clean_Lifecycle_Bindings"></a></h4>
<table border="1" class="bodyTable">
@@ -514,7 +514,7 @@
<table border="1" class="bodyTable">
<tr class="a">
<td align="left"><tt>generate-resources</tt></td>
-<td align="left"><tt>ear:generateApplicationXml</tt></td></tr>
+<td align="left"><tt>ear:generate-application-xml</tt></td></tr>
<tr class="b">
<td align="left"><tt>process-resources</tt></td>
<td align="left"><tt>resources:resources</tt></td></tr>
@@ -553,7 +553,7 @@
<td align="left"><tt>jar:jar</tt> <i>and</i>
<tt>plugin:addPluginArtifactMetadata</tt></td></tr>
<tr class="b">
<td align="left"><tt>install</tt></td>
-<td align="left"><tt>install:install</tt> <i>and</i>
<tt>plugin:updateRegistry</tt></td></tr>
+<td align="left"><tt>install:install</tt></td></tr>
<tr class="a">
<td align="left"><tt>deploy</tt></td>
<td align="left"><tt>deploy:deploy</tt></td></tr></table></div>
@@ -580,7 +580,9 @@
<td align="left"><tt>site:deploy</tt></td></tr></table></div>
<div class="section">
<h4>References<a name="References"></a></h4>
-<p>The full Maven lifecycle is defined by the file <tt>components.xml</tt> in
the module <tt>maven-core</tt> and viewable from SVN in the branches for <a
class="externalLink"
href="http://svn.apache.org/repos/asf/maven/maven-2/tags/maven-2.2.0/maven-core/src/main/resources/META-INF/plexus/components.xml";>Maven
2.2.0</a> and <a class="externalLink"
href="http://svn.apache.org/repos/asf/maven/maven-3/trunk/maven-core/src/main/resources/META-INF/plexus/components.xml";>Maven
3.0.x</a>.</p>
+<p>The full Maven lifecycle is defined by the file <tt>components.xml</tt> in
the module <tt>maven-core</tt> and viewable from SVN in the branch for <a
class="externalLink"
href="http://svn.apache.org/repos/asf/maven/maven-2/tags/maven-2.2.1/maven-core/src/main/resources/META-INF/plexus/components.xml";>Maven
2.2.1</a> and Git for <a class="externalLink"
href="https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-core/src/main/resources/META-INF/plexus/components.xml";>Maven
3.x</a>.</p>
+<p>In Maven 2.x, default lifecycle bindings were included in
<tt>components.xml</tt>, but in Maven 3.x, they are defined in a separate
<tt><a class="externalLink"
href="https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-core/src/main/resources/META-INF/plexus/default-bindings.xml";>default-bindings.xml</a></tt>
descriptor.</p>
+<p>See <a href="/ref/current/maven-core/lifecycles.html">Lifecycles
Reference</a> and <a
href="/ref/current/maven-core/default-bindings.html">Plugin Bindings for
default Lifecycle Reference</a> for latest documentation taken directly from
source code.</p>
<p><i><a
href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div></div></div>
</div>
</div>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
