You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by bu...@apache.org on 2015/04/05 00:10:41 UTC
svn commit: r946345 - in /websites/staging/maven/trunk/content: ./
guides/introduction/introduction-to-the-lifecycle.html
maven-site-1.0-site.jar
Author: buildbot
Date: Sat Apr 4 22:10:40 2015
New Revision: 946345
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 Sat Apr 4 22:10:40 2015
@@ -1 +1 @@
-1671352
+1671355
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 Sat Apr 4 22:10:40 2015
@@ -247,7 +247,7 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- Copyright 2006 The Apache Software Foundation. --><!-- --><!-- Licensed under the Apache License, Version 2.0 (the "License"); --><!-- you may not use this file except in compliance with the License. --><!-- You may obtain a copy of the License at --><!-- --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!-- --><!-- Unless required by applicable law or agreed to in writing, software --><!-- distributed under the License is distributed on an "AS IS" BASIS, --><!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. --><!-- See the License for the specific language governing permissions and --><!-- limitations under the License. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/references/apt-format.html --><div class="section">
+ <!-- Copyright 2015 The Apache Software Foundation. --><!-- --><!-- Licensed under the Apache License, Version 2.0 (the "License"); --><!-- you may not use this file except in compliance with the License. --><!-- You may obtain a copy of the License at --><!-- --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!-- --><!-- Unless required by applicable law or agreed to in writing, software --><!-- distributed under the License is distributed on an "AS IS" BASIS, --><!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. --><!-- See the License for the specific language governing permissions and --><!-- limitations under the License. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/references/apt-format.html --><div class="section">
<h2><a name="Introduction_to_the_Build_Lifecycle"></a>Introduction to the Build Lifecycle</h2>
<div class="section">
<h3><a name="Table_Of_Contents"></a>Table Of Contents</h3>
@@ -261,13 +261,13 @@
<li><a href="#Built-in_Lifecycle_Bindings">Built-in Lifecycle Bindings</a></li></ul></div>
<div class="section">
<h3><a name="Build_Lifecycle_Basics">Build Lifecycle Basics</a></h3>
-<p>Maven 2.0 is based around the central concept of a build lifecycle. What this means is that the process for building and distributing a particular artifact (project) is clearly defined.</p>
+<p>Maven is based around the central concept of a build lifecycle. What this means is that the process for building and distributing a particular artifact (project) is clearly defined.</p>
<p>For the person building a project, this means that it is only necessary to learn a small set of commands to build any Maven project, and the <a href="./introduction-to-the-pom.html">POM</a> will ensure they get the results they desired.</p>
-<p>There are three built-in build lifecycles: default, clean and site. The default lifecycle handles your project deployment, the clean lifecycle handles project cleaning, while the site lifecycle handles the creation of your project's site documentation.</p>
+<p>There are three built-in build lifecycles: default, clean and site. The <tt>default</tt> lifecycle handles your project deployment, the <tt>clean</tt> lifecycle handles project cleaning, while the <tt>site</tt> lifecycle handles the creation of your project's site documentation.</p>
<div class="section">
<h4><a name="A_Build_Lifecycle_is_Made_Up_of_Phases">A Build Lifecycle is Made Up of Phases</a></h4>
<p>Each of these build lifecycles is defined by a different list of build phases, wherein a build phase represents a stage in the lifecycle.</p>
-<p>For example, the default lifecycle has the following build phases (for a complete list of the build phases, refer to the <a href="#Lifecycle_Reference">Lifecycle Reference</a>):</p>
+<p>For example, the default lifecycle comprises of the following phases (for a complete list of the lifecycle phases, refer to the <a href="#Lifecycle_Reference">Lifecycle Reference</a>):</p>
<ul>
<li><tt>validate</tt> - validate the project is correct and all necessary information is available</li>
<li><tt>compile</tt> - compile the source code of the project</li>
@@ -277,14 +277,14 @@
<li><tt>verify</tt> - run any checks to verify the package is valid and meets quality criteria</li>
<li><tt>install</tt> - install the package into the local repository, for use as a dependency in other projects locally</li>
<li><tt>deploy</tt> - done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.</li></ul>
-<p>These build phases (plus the other build phases not shown here) are executed sequentially to complete the default lifecycle. Given the build phases above, this means that when the default lifecycle is used, Maven will first validate the project, then will try to compile the sources, run those against the tests, package the binaries (e.g. jar), run integration tests against that package, verify the package, install the verifed package to the local repository, then deploy the installed package in a specified environment.</p>
+<p>These lifecycle phases (plus the other lifecycle phases not shown here) are executed sequentially to complete the <tt>default</tt> lifecycle. Given the lifecycle phases above, this means that when the default lifecycle is used, Maven will first validate the project, then will try to compile the sources, run those against the tests, package the binaries (e.g. jar), run integration tests against that package, verify the package, install the verifed package to the local repository, then deploy the installed package in a specified environment.</p>
<p>To do all those, you only need to call the last build phase to be executed, in this case, <tt>deploy</tt>:</p>
<div>
<pre>mvn deploy</pre></div>
<p>That is because if you call a build phase, it will execute not only that build phase, but also every build phase prior to the called build phase. Thus, doing</p>
<div>
<pre>mvn integration-test</pre></div>
-<p>will do every build phase before it (<tt>validate</tt>, <tt>compile</tt>, <tt>package</tt>, etc.), before executing <tt>integration-test</tt>.</p>
+<p>will do every life cycle phase before it (<tt>validate</tt>, <tt>compile</tt>, <tt>package</tt>, etc.), before executing <tt>integration-test</tt>.</p>
<p>There are more commands that are part of the lifecycle, which will be discussed in the following sections.</p>
<p>It should also be noted that the same command can be used in a multi-module scenario (i.e. a project with one or more subprojects). For example:</p>
<div>
@@ -299,7 +299,8 @@
<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>
<p>Moreover, if a goal is bound to one or more build phases, that goal will be called in all those phases.</p>
-<p>Furthermore, a build phase can also have zero or more goals bound to it. If a build phase has no goals bound to it, that build phase will not execute. But if it has one or more goals bound to it, it will execute all those goals (<i>Note: In Maven 2.0.5 and above, multiple goals bound to a phase are executed in the same order as they are declared in the POM, however multiple instances of the same plugin are not supported. Multiple instances of the same plugin are grouped to execute together and ordered in Maven 2.0.11 and above</i>).</p>
+<p>Furthermore, a build phase can also have zero or more goals bound to it. If a build phase has no goals bound to it, that build phase will not execute. But if it has one or more goals bound to it, it will execute all those goals</p><!-- ~ --><!-- ~ Check if the following is true for Maven 3... -->
+<p>(<i>Note: In Maven 2.0.5 and above, multiple goals bound to a phase are executed in the same order as they are declared in the POM, however multiple instances of the same plugin are not supported. Multiple instances of the same plugin are grouped to execute together and ordered in Maven 2.0.11 and above</i>).</p><!-- ~ -->
<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div></div>
<div class="section">
<h3><a name="Setting_Up_Your_Project_to_Use_the_Build_Lifecycle">Setting Up Your Project to Use the Build Lifecycle</a></h3>
@@ -333,7 +334,7 @@
<tr class="b">
<td align="left"><tt>deploy</tt></td>
<td align="left"><tt>deploy:deploy</tt></td></tr></table>
-<p>This is an almost standard set of bindings; however, some packagings handle them differently. For example, a project that is purely metadata (packaging value is <tt>pom</tt>) only binds goals to the <tt>install</tt> and <tt>deploy</tt> phases (for a complete list of goal-to-build-phase bindings of some of the packaging types, refer to the <a href="#Lifecycle_Reference">Lifecycle Reference</a>).</p>
+<p>This is an almost <a href="/ref/current/maven-core/default-bindings.html">standard set of bindings</a>; however, some packagings handle them differently. For example, a project that is purely metadata (packaging value is <tt>pom</tt>) only binds goals to the <tt>install</tt> and <tt>deploy</tt> phases (for a complete list of goal-to-build-phase bindings of some of the packaging types, refer to the <a href="#Lifecycle_Reference">Lifecycle Reference</a>).</p>
<p>Note that for some packaging types to be available, you may also need to include a particular plugin in the <tt><build></tt> section of your POM and specify <tt><extensions>true</extensions></tt> for that plugin. One example of a plugin that requires this is the Plexus plugin, which provides a <tt>plexus-application</tt> and <tt>plexus-service</tt> packaging.</p>
<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div>
<div class="section">
@@ -347,7 +348,7 @@
<plugin>
<groupId>org.codehaus.modello</groupId>
<artifactId>modello-maven-plugin</artifactId>
- <version>1.4</version>
+ <version>1.8.1</version>
<executions>
<execution>
<configuration>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.