You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by bu...@apache.org on 2013/04/27 09:29:25 UTC
svn commit: r860084 [16/39] - in /websites/staging/maven/trunk/content: ./
background/ developers/ developers/conventions/ developers/release/
developers/website/ docs/2.0.1/ docs/2.0.10/ docs/2.0.11/ docs/2.0.2/
docs/2.0.3/ docs/2.0.4/ docs/2.0.5/ doc...
Modified: websites/staging/maven/trunk/content/guides/getting-started/maven-in-five-minutes.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/getting-started/maven-in-five-minutes.html (original)
+++ websites/staging/maven/trunk/content/guides/getting-started/maven-in-five-minutes.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Eric Redmond" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Maven in 5 Minutes
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -248,12 +248,39 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Maven in 5 Minutes<a name="Maven_in_5_Minutes"></a></h2><div class="section"><h3>Prerequisites<a name="Prerequisites"></a></h3><p>You must have an understanding of how to install software on your computer. If you do not know how to do this, please ask someone at your office, school, etc or pay someone to explain this to you. The Maven mailing lists are not the best place to ask for this advice.</p></div><div class="section"><h3>Installation<a name="Installation"></a></h3><p><i>Maven is a Java tool, so you must have <a class="externalLink" href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Java</a> installed in order to proceed.</i></p><p>First, <a href="../../download.html">download Maven</a> and follow the <a href="../../download.html#Installation">installation instructions</a>. After that, type the following in a terminal or in a command prompt:</p><div class="source"><pre>mvn --version</pre></div><p>It should print o
ut your installed version of Maven, for example:</p><div class="source"><pre>Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
+ <div class="section">
+<h2>Maven in 5 Minutes<a name="Maven_in_5_Minutes"></a></h2>
+<div class="section">
+<h3>Prerequisites<a name="Prerequisites"></a></h3>
+<p>You must have an understanding of how to install software on your computer. If you do not know how to do this, please ask someone at your office, school, etc or pay someone to explain this to you. The Maven mailing lists are not the best place to ask for this advice.</p></div>
+<div class="section">
+<h3>Installation<a name="Installation"></a></h3>
+<p><i>Maven is a Java tool, so you must have <a class="externalLink" href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Java</a> installed in order to proceed.</i></p>
+<p>First, <a href="../../download.html">download Maven</a> and follow the <a href="../../download.html#Installation">installation instructions</a>. After that, type the following in a terminal or in a command prompt:</p>
+<div class="source">
+<pre>mvn --version</pre></div>
+<p>It should print out your installed version of Maven, for example:</p>
+<div class="source">
+<pre>Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: D:\apache-maven-3.0.3\bin\..
Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
Java home: E:\Program Files\Java\jdk1.6.0_25\jre
Default locale: nl_NL, platform encoding: Cp1252
-OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"</pre></div><p>Depending upon your network setup, you may require extra configuration. Check out the <a href="../mini/guide-configuring-maven.html">Guide to Configuring Maven</a> if necessary.</p><p><b>If you are using Windows, you should look at</b> <a href="./windows-prerequisites.html">Windows Prerequisites</a> <b>to ensure that you are prepared to use Maven on Windows.</b></p></div><div class="section"><h3>Creating a Project<a name="Creating_a_Project"></a></h3><p>You will need somewhere for your project to reside, create a directory somewhere and start a shell in that directory. On your command line, execute the following Maven goal:</p><div class="source"><pre>mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false</pre></div><p><i>If you have just installed Maven, it may ta
ke a while on the first run. This is because Maven is downloading the most recent artifacts (plugin jars and other files) into your local repository. You may also need to execute the command a couple of times before it succeeds. This is because the remote server may time out before your downloads are complete. Don't worry, there are ways to fix that.</i></p><p>You will notice that the <i>generate</i> goal created a directory with the same name given as the artifactId. Change into that directory.</p><div class="source"><pre>cd my-app</pre></div><p>Under this directory you will notice the following <a href="../introduction/introduction-to-the-standard-directory-layout.html">standard project structure</a>.</p><div class="source"><pre>my-app
+OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"</pre></div>
+<p>Depending upon your network setup, you may require extra configuration. Check out the <a href="../mini/guide-configuring-maven.html">Guide to Configuring Maven</a> if necessary.</p>
+<p><b>If you are using Windows, you should look at</b> <a href="./windows-prerequisites.html">Windows Prerequisites</a> <b>to ensure that you are prepared to use Maven on Windows.</b></p></div>
+<div class="section">
+<h3>Creating a Project<a name="Creating_a_Project"></a></h3>
+<p>You will need somewhere for your project to reside, create a directory somewhere and start a shell in that directory. On your command line, execute the following Maven goal:</p>
+<div class="source">
+<pre>mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false</pre></div>
+<p><i>If you have just installed Maven, it may take a while on the first run. This is because Maven is downloading the most recent artifacts (plugin jars and other files) into your local repository. You may also need to execute the command a couple of times before it succeeds. This is because the remote server may time out before your downloads are complete. Don't worry, there are ways to fix that.</i></p>
+<p>You will notice that the <i>generate</i> goal created a directory with the same name given as the artifactId. Change into that directory.</p>
+<div class="source">
+<pre>cd my-app</pre></div>
+<p>Under this directory you will notice the following <a href="../introduction/introduction-to-the-standard-directory-layout.html">standard project structure</a>.</p>
+<div class="source">
+<pre>my-app
|-- pom.xml
`-- src
|-- main
@@ -267,7 +294,13 @@ OS name: "windows 7", version:
`-- com
`-- mycompany
`-- app
- `-- AppTest.java</pre></div><p>The <tt>src/main/java</tt> directory contains the project source code, the <tt>src/test/java</tt> directory contains the test source, and the <tt>pom.xml</tt> file is the project's Project Object Model, or POM.</p><div class="section"><h4>The POM<a name="The_POM"></a></h4><p>The <tt>pom.xml</tt> file is the core of a project's configuration in Maven. It is a single configuration file that contains the majority of information required to build a project in just the way you want. The POM is huge and can be daunting in its complexity, but it is not necessary to understand all of the intricacies just yet to use it effectively. This project's POM is:</p><div class="source"><pre><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ `-- AppTest.java</pre></div>
+<p>The <tt>src/main/java</tt> directory contains the project source code, the <tt>src/test/java</tt> directory contains the test source, and the <tt>pom.xml</tt> file is the project's Project Object Model, or POM.</p>
+<div class="section">
+<h4>The POM<a name="The_POM"></a></h4>
+<p>The <tt>pom.xml</tt> file is the core of a project's configuration in Maven. It is a single configuration file that contains the majority of information required to build a project in just the way you want. The POM is huge and can be daunting in its complexity, but it is not necessary to understand all of the intricacies just yet to use it effectively. This project's POM is:</p>
+<div class="source">
+<pre><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -287,14 +320,70 @@ OS name: "windows 7", version:
<scope>test</scope>
</dependency>
</dependencies>
-</project></pre></div></div><div class="section"><h4>What did I just do?<a name="What_did_I_just_do"></a></h4><p>You executed the Maven goal <i>archetype:generate</i>, and passed in various parameters to that goal. The prefix <i>archetype</i> is the <a href="../../plugins/index.html">plugin</a> that contains the goal. If you are familiar with <a class="externalLink" href="http://ant.apache.org">Ant</a>, you may conceive of this as similar to a task. This goal created a simple project based upon an archetype. Suffice it to say for now that a <i>plugin</i> is a collection of <i>goals</i> with a general common purpose. For example the jboss-maven-plugin, whose purpose is "deal with various jboss items".</p></div><div class="section"><h4>Build the Project<a name="Build_the_Project"></a></h4><div class="source"><pre>mvn package</pre></div><p>The command line will print out various actions, and end with the following:</p><div class="source"><pre> ...
+</project></pre></div></div>
+<div class="section">
+<h4>What did I just do?<a name="What_did_I_just_do"></a></h4>
+<p>You executed the Maven goal <i>archetype:generate</i>, and passed in various parameters to that goal. The prefix <i>archetype</i> is the <a href="../../plugins/index.html">plugin</a> that contains the goal. If you are familiar with <a class="externalLink" href="http://ant.apache.org">Ant</a>, you may conceive of this as similar to a task. This goal created a simple project based upon an archetype. Suffice it to say for now that a <i>plugin</i> is a collection of <i>goals</i> with a general common purpose. For example the jboss-maven-plugin, whose purpose is "deal with various jboss items".</p></div>
+<div class="section">
+<h4>Build the Project<a name="Build_the_Project"></a></h4>
+<div class="source">
+<pre>mvn package</pre></div>
+<p>The command line will print out various actions, and end with the following:</p>
+<div class="source">
+<pre> ...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Jul 07 21:34:52 CEST 2011
[INFO] Final Memory: 3M/6M
-[INFO] ------------------------------------------------------------------------</pre></div><p>Unlike the first command executed (<i>archetype:generate</i>) you may notice the second is simply a single word - <i>package</i>. Rather than a goal, this is a <i>phase</i>. A phase is a step in the <a href="../introduction/introduction-to-the-lifecycle.html">build lifecycle</a>, which is an ordered sequence of phases. When a phase is given, Maven will execute every phase in the sequence up to and including the one defined. For example, if we execute the <i>compile</i> phase, the phases that actually get executed are:</p><ol style="list-style-type: decimal"><li>validate</li><li>generate-sources</li><li>process-sources</li><li>generate-resources</li><li>process-resources</li><li>compile</li></ol><p>You may test the newly compiled and packaged JAR with the following command:</p><div class="source"><pre>java -cp target/my-app-1.0-SNAPSHOT.jar com.mycompany.app.App</pre></div><p>Which w
ill print the quintessential:</p><div class="source"><pre>Hello World!</pre></div></div></div><div class="section"><h3>Running Maven Tools<a name="Running_Maven_Tools"></a></h3><div class="section"><h4>Maven Phases<a name="Maven_Phases"></a></h4><p>Although hardly a comprehensive list, these are the most common <i>default</i> lifecycle phases executed.</p><ul><li><b>validate</b>: validate the project is correct and all necessary information is available</li><li><b>compile</b>: compile the source code of the project</li><li><b>test</b>: test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed</li><li><b>package</b>: take the compiled code and package it in its distributable format, such as a JAR.</li><li><b>integration-test</b>: process and deploy the package if necessary into an environment where integration tests can be run</li><li><b>verify</b>: run any checks to verify the package is valid and m
eets quality criteria</li><li><b>install</b>: install the package into the local repository, for use as a dependency in other projects locally</li><li><b>deploy</b>: 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>There are two other Maven lifecycles of note beyond the <i>default</i> list above. They are</p><ul><li><b>clean</b>: cleans up artifacts created by prior builds</li></ul><ul><li><b>site</b>: generates site documentation for this project</li></ul><p>Phases are actually mapped to underlying goals. The specific goals executed per phase is dependant upon the packaging type of the project. For example, <i>package</i> executes <i>jar:jar</i> if the project type is a JAR, and <i>war:war</i> is the project type is - you guessed it - a WAR.</p><p>An interesting thing to note is that phases and goals may be executed in sequence.</p><div class="source"><pre>mvn clean d
ependency:copy-dependencies package</pre></div><p>This command will clean the project, copy dependencies, and package the project (executing all phases up to <i>package</i>, of course).</p></div><div class="section"><h4>Generating the Site<a name="Generating_the_Site"></a></h4><div class="source"><pre>mvn site</pre></div><p>This phase generates a site based upon information on the project's pom. You can look at the documentation generated under <tt>target/site</tt>.</p></div></div><div class="section"><h3>Conclusion<a name="Conclusion"></a></h3><p>We hope this quick overview has piqued your interest in the versitility of Maven. Note that this is a very truncated quick-start guide. Now you are ready for more comprehensive details concerning the actions you have just performed. Check out the <a href="./index.html">Maven Getting Started Guide</a>.</p></div></div>
+[INFO] ------------------------------------------------------------------------</pre></div>
+<p>Unlike the first command executed (<i>archetype:generate</i>) you may notice the second is simply a single word - <i>package</i>. Rather than a goal, this is a <i>phase</i>. A phase is a step in the <a href="../introduction/introduction-to-the-lifecycle.html">build lifecycle</a>, which is an ordered sequence of phases. When a phase is given, Maven will execute every phase in the sequence up to and including the one defined. For example, if we execute the <i>compile</i> phase, the phases that actually get executed are:</p>
+<ol style="list-style-type: decimal">
+<li>validate</li>
+<li>generate-sources</li>
+<li>process-sources</li>
+<li>generate-resources</li>
+<li>process-resources</li>
+<li>compile</li></ol>
+<p>You may test the newly compiled and packaged JAR with the following command:</p>
+<div class="source">
+<pre>java -cp target/my-app-1.0-SNAPSHOT.jar com.mycompany.app.App</pre></div>
+<p>Which will print the quintessential:</p>
+<div class="source">
+<pre>Hello World!</pre></div></div></div>
+<div class="section">
+<h3>Running Maven Tools<a name="Running_Maven_Tools"></a></h3>
+<div class="section">
+<h4>Maven Phases<a name="Maven_Phases"></a></h4>
+<p>Although hardly a comprehensive list, these are the most common <i>default</i> lifecycle phases executed.</p>
+<ul>
+<li><b>validate</b>: validate the project is correct and all necessary information is available</li>
+<li><b>compile</b>: compile the source code of the project</li>
+<li><b>test</b>: test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed</li>
+<li><b>package</b>: take the compiled code and package it in its distributable format, such as a JAR.</li>
+<li><b>integration-test</b>: process and deploy the package if necessary into an environment where integration tests can be run</li>
+<li><b>verify</b>: run any checks to verify the package is valid and meets quality criteria</li>
+<li><b>install</b>: install the package into the local repository, for use as a dependency in other projects locally</li>
+<li><b>deploy</b>: 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>There are two other Maven lifecycles of note beyond the <i>default</i> list above. They are</p>
+<ul>
+<li><b>clean</b>: cleans up artifacts created by prior builds</li></ul>
+<ul>
+<li><b>site</b>: generates site documentation for this project</li></ul>
+<p>Phases are actually mapped to underlying goals. The specific goals executed per phase is dependant upon the packaging type of the project. For example, <i>package</i> executes <i>jar:jar</i> if the project type is a JAR, and <i>war:war</i> is the project type is - you guessed it - a WAR.</p>
+<p>An interesting thing to note is that phases and goals may be executed in sequence.</p>
+<div class="source">
+<pre>mvn clean dependency:copy-dependencies package</pre></div>
+<p>This command will clean the project, copy dependencies, and package the project (executing all phases up to <i>package</i>, of course).</p></div>
+<div class="section">
+<h4>Generating the Site<a name="Generating_the_Site"></a></h4>
+<div class="source">
+<pre>mvn site</pre></div>
+<p>This phase generates a site based upon information on the project's pom. You can look at the documentation generated under <tt>target/site</tt>.</p></div></div>
+<div class="section">
+<h3>Conclusion<a name="Conclusion"></a></h3>
+<p>We hope this quick overview has piqued your interest in the versitility of Maven. Note that this is a very truncated quick-start guide. Now you are ready for more comprehensive details concerning the actions you have just performed. Check out the <a href="./index.html">Maven Getting Started Guide</a>.</p></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/guides/getting-started/windows-prerequisites.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/getting-started/windows-prerequisites.html (original)
+++ websites/staging/maven/trunk/content/guides/getting-started/windows-prerequisites.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Benson Margulies" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Maven on Windows
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -231,7 +231,28 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Maven on Windows<a name="Maven_on_Windows"></a></h2><p>Maven is a command-line tool for building Java (and other) programs. The Maven project provides a simple ZIP file containing a precompiled version of Maven for your convenience. There is no installer. It's up to you to set up your prerequisites and environment to run Maven on Windows.</p><div class="section"><h3>Spaces in Pathnames<a name="Spaces_in_Pathnames"></a></h3><p>Maven, like many cross-platform tools, can encounter problems when there are space characters in important pathnames. The instructions below will remind you of this for several particular items.</p></div><div class="section"><h3>Prerequisites<a name="Prerequisites"></a></h3><p>Maven is written in Java (and primarily used to build Java programs). Thus, the major prerequisite is the Java SDK. You need to install the Java SDK (e.g. from <a class="externalLink" href="http://www.oracle.com/technetwork/java/javase/downloads/in
dex.html} Oracle's download site">http://www.oracle.com/technetwork/java/javase/downloads/index.html} Oracle's download site</a>, and you should install it to a pathname without spaces, such as <tt>c:\j2se1.6</tt>.</p><p>Once Java is installed, you must ensure that the commands from the Java SDK are in your PATH environment variable. Running, for example,</p><div class="source"><pre>java -version</pre></div><p>must show the right version number.</p></div><div class="section"><h3>Maven Unpacked<a name="Maven_Unpacked"></a></h3><p>You need to unpack the Maven distribution. Don't unpack it in the middle of your source code; pick some location (with no spaces in the path!) and unpack it there. Let's assume that the path is <tt>c:\mvn3.0.4</tt>.</p></div><div class="section"><h3>Maven in PATH<a name="Maven_in_PATH"></a></h3><p>You run Maven by invoking a command-line tool: <tt>mvn.bat</tt> from the <tt>bin</tt> directory of the Maven. To do this conveniently, <tt>c:\mvn3.0.4
\bin</tt> must be in your PATH, just like the J2SE SDK commands. You can add directories to your PATH in the control panel; the details vary by Windows version.</p></div><div class="section"><h3>Firewalls and Anti-virus<a name="Firewalls_and_Anti-virus"></a></h3><p>Firewall and Anti-virus sometimes prevent Java from running properly, or Windows Firewall (and various other Firewalls) actively prevent Java.exe from reaching out to the Internet to "download stuff" which is a key part of Maven You may need to configure the Firewall or Anti-virus to add exceptions to allow such actions.</p></div></div>
+ <div class="section">
+<h2>Maven on Windows<a name="Maven_on_Windows"></a></h2>
+<p>Maven is a command-line tool for building Java (and other) programs. The Maven project provides a simple ZIP file containing a precompiled version of Maven for your convenience. There is no installer. It's up to you to set up your prerequisites and environment to run Maven on Windows.</p>
+<div class="section">
+<h3>Spaces in Pathnames<a name="Spaces_in_Pathnames"></a></h3>
+<p>Maven, like many cross-platform tools, can encounter problems when there are space characters in important pathnames. The instructions below will remind you of this for several particular items.</p></div>
+<div class="section">
+<h3>Prerequisites<a name="Prerequisites"></a></h3>
+<p>Maven is written in Java (and primarily used to build Java programs). Thus, the major prerequisite is the Java SDK. You need to install the Java SDK (e.g. from <a class="externalLink" href="http://www.oracle.com/technetwork/java/javase/downloads/index.html} Oracle's download site">http://www.oracle.com/technetwork/java/javase/downloads/index.html} Oracle's download site</a>, and you should install it to a pathname without spaces, such as <tt>c:\j2se1.6</tt>.</p>
+<p>Once Java is installed, you must ensure that the commands from the Java SDK are in your PATH environment variable. Running, for example,</p>
+<div class="source">
+<pre>java -version</pre></div>
+<p>must show the right version number.</p></div>
+<div class="section">
+<h3>Maven Unpacked<a name="Maven_Unpacked"></a></h3>
+<p>You need to unpack the Maven distribution. Don't unpack it in the middle of your source code; pick some location (with no spaces in the path!) and unpack it there. Let's assume that the path is <tt>c:\mvn3.0.4</tt>.</p></div>
+<div class="section">
+<h3>Maven in PATH<a name="Maven_in_PATH"></a></h3>
+<p>You run Maven by invoking a command-line tool: <tt>mvn.bat</tt> from the <tt>bin</tt> directory of the Maven. To do this conveniently, <tt>c:\mvn3.0.4\bin</tt> must be in your PATH, just like the J2SE SDK commands. You can add directories to your PATH in the control panel; the details vary by Windows version.</p></div>
+<div class="section">
+<h3>Firewalls and Anti-virus<a name="Firewalls_and_Anti-virus"></a></h3>
+<p>Firewall and Anti-virus sometimes prevent Java from running properly, or Windows Firewall (and various other Firewalls) actively prevent Java.exe from reaching out to the Internet to "download stuff" which is a key part of Maven You may need to configure the Firewall or Anti-virus to add exceptions to allow such actions.</p></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/guides/index.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/index.html (original)
+++ websites/staging/maven/trunk/content/guides/index.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -15,7 +15,7 @@
<meta name="author" content="Jason van Zyl
Eric Redmond" />
<meta name="Date-Creation-yyyymmdd" content="20090801" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ Eric Redmond" />
Maven Documentation
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -233,7 +233,136 @@ Eric Redmond" />
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements. See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership. The ASF licenses this file --><!-- to you 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/referen
ces/apt-format.html --><div class="section"><h2>Documentation<a name="Documentation"></a></h2><div class="section"><h3>Getting Started with Maven<a name="Getting_Started_with_Maven"></a></h3><ul><li><a href="./getting-started/maven-in-five-minutes.html">Getting Started in 5 Minutes</a></li><li><a href="./getting-started/index.html">Getting Started in 30 Minutes</a></li></ul></div><div class="section"><h3>Introductions<a name="Introductions"></a></h3><ul><li><a href="./introduction/introduction-to-the-lifecycle.html">The Build Lifecycle</a></li><li><a href="./introduction/introduction-to-the-pom.html">The POM</a></li><li><a href="./introduction/introduction-to-profiles.html">Profiles</a></li><li><a href="./introduction/introduction-to-repositories.html">Repositories</a></li><li><a href="./introduction/introduction-to-the-standard-directory-layout.html">Standard Directory Layout</a></li><li><a href="./introduction/introduction-to-dependency-mechanism.html">The Dependency Mecha
nism</a></li><li><a href="./introduction/introduction-to-optional-and-excludes-dependencies.html"> Optional Dependencies and Dependency Exclusions</a></li></ul><div class="section"><h4>Plugins<a name="Plugins"></a></h4><ul><li><a href="./introduction/introduction-to-plugins.html">Plugin Development</a></li><li><a href="./mini/guide-configuring-plugins.html">Configuring Plug-ins</a></li><li><a href="./introduction/introduction-to-plugin-registry.html">The Plugin Registry</a></li><li><a href="./introduction/introduction-to-plugin-prefix-mapping.html">Plugin Prefix Resolution</a></li><li><a href="./introduction/introduction-to-plugin-resolution.html"> Introduction to Maven Plugin Resolution</a></li><li><a href="./plugin/guide-ant-plugin-development.html">Developing Ant Plugins</a></li><li><a href="./plugin/guide-java-plugin-development.html">Developing Java Plugins</a></li></ul></div><div class="section"><h4>Site<a name="Site"></a></h4><ul><li><a href="./mini/guide-site.html">C
reating a Site</a></li><li><a class="externalLink" href="http://maven.apache.org/doxia/references/apt-format.html">The APT Format</a></li><li><a href="./mini/guide-snippet-macro.html">Snippet Macro</a></li></ul></div><div class="section"><h4>Archetypes<a name="Archetypes"></a></h4><ul><li><a href="./introduction/introduction-to-archetypes.html">What is an Archetype</a></li><li><a href="./mini/guide-creating-archetypes.html">Creating Archetypes</a></li></ul></div><div class="section"><h4>Upgrading<a name="Upgrading"></a></h4><ul><li><a href="./mini/guide-m1-m2.html">From Maven 1.x to Maven 2.x</a></li><li><a href="./mini/guide-using-m1-repos-with-m2.html">Using Maven 1.x repositories with Maven 2.x</a></li><li><a href="./mini/guide-relocation.html">Relocation of Artifacts</a></li></ul></div><div class="section"><h4>Repositories<a name="Repositories"></a></h4><ul><li><a href="./mini/guide-3rd-party-jars-local.html">Installing 3rd party JARs to Local Repository</a></li><li><a h
ref="./mini/guide-3rd-party-jars-remote.html">Deploying 3rd party JARs to Remote Repository</a></li><li><a href="./mini/guide-coping-with-sun-jars.html">Coping with Sun JARs</a></li><li><a href="./mini/guide-repository-ssl.html">Remote repository access through authenticated HTTPS</a></li></ul><!-- * {{{./introduction/introduction-to-artifact-resolution.html}Repository Definitions and Artifact Resolution}} --></div></div><div class="section"><h3>Guides<a name="Guides"></a></h3><ul><li><a href="./mini/guide-assemblies.html">Creating Assemblies</a></li><li><a href="./mini/guide-archive-configuration.html">Configuring Archive Plugins</a></li><li><a href="./mini/guide-configuring-maven.html">Configuring Maven</a></li><li><a href="./mini/guide-mirror-settings.html">Mirror Settings</a></li><li><a href="./mini/guide-deployment-security-settings.html">Deployment and Security Settings</a></li><li><a href="./mini/guide-generating-sources.html">Generating Sources</a></li><li><a href=".
/mini/guide-manifest.html">Working with Manifests</a></li><li><a href="./mini/guide-maven-classloading.html">Maven Classloading</a></li><li><a href="./mini/guide-multiple-modules.html">Using Multiple Modules in a Build</a></li><li><a href="./mini/guide-multiple-repositories.html">Using Multiple Repositories</a></li><li><a href="./mini/guide-proxies.html">Using Proxies</a></li><li><a href="./mini/guide-releasing.html">Using the Release Plugin</a></li><li><a href="./mini/guide-using-ant.html">Using Ant with Maven</a></li><li><a href="./mini/guide-using-modello.html">Using Modello</a></li><li><a href="./mini/guide-webapp.html">Webapps</a></li><li><a href="./mini/guide-using-extensions.html">Using Extensions</a></li><li><a href="./mini/guide-building-for-different-environments.html">Building For Different Environments with Maven 2</a></li><li><a href="./mini/guide-using-toolchains.html">Using Toolchains</a></li><li><a href="./mini/guide-encryption.html"> Encrypting passwords in
settings.xml</a></li><li><a href="./mini/guide-http-settings.html"> Guide to HTTP Connection Settings</a></li><li><a href="./mini/guide-wagon-providers.html"> Guide to Selecting Alternative Wagon Providers</a></li><li><a href="./mini/guide-building-jdk14-on-jdk15.html"> Guide to Building JDK 1.4 Projects Using JDK 1.5</a></li><li><a href="./mini/guide-default-execution-ids.html"> Guide to Configuring Default Mojo Executions</a></li></ul><!-- ** Testing --><!-- * {{{./mini/guide-attached-tests.html}Reusable Test JARs}} --><div class="section"><h4>Maven Tools and IDE Integration<a name="Maven_Tools_and_IDE_Integration"></a></h4><ul><li><a href="./mini/guide-ide-eclipse.html">Eclipse</a></li><li><a href="./mini/guide-ide-idea.html">IDEA</a></li><li><a href="./mini/guide-ide-netbeans/guide-ide-netbeans.html">NetBeans 4.0 (4.1 and 5.0)</a></li><li><a href="./mini/guide-bash-m2-completion.html">Maven 2.x Auto-Completion Using BASH</a></li></ul></div></div><div class="section"><h3>
Development Guides<a name="Development_Guides"></a></h3><ul><li><a href="./development/guide-building-m2.html">Building Maven from Scratch</a></li><li><a href="./development/guide-m2-development.html">Developing Maven</a></li><li><a href="./development/guide-plugin-documentation.html">The Plugin Documentation Standard</a></li><li><a href="./development/guide-documentation-style.html">Maven Documentation Style</a></li></ul></div><div class="section"><h3>The Maven Community<a name="The_Maven_Community"></a></h3><ul><li><a href="../community.html">The Maven Community</a></li><li><a href="./development/guide-helping.html">Helping with Maven</a></li><li><a href="./mini/guide-new-committers.html">Guide for New Committers</a></li><li><a href="./development/guide-testing-development-plugins.html">Testing Development Versions of Plugins</a></li><li><a href="../articles.html">3rd Party Resources</a></li></ul><div class="section"><h4>Conventions<a name="Conventions"></a></h4><ul><li><a
href="../maven-conventions.html">Maven Conventions</a></li><li><a href="./mini/guide-naming-conventions.html">Naming Conventions</a></li><li><a href="./mini/guide-using-one-source-directory.html">When You Can't Use the Conventions</a></li></ul></div><div class="section"><h4>The Central Repository<a name="The_Central_Repository"></a></h4><ul><li><a href="./mini/guide-central-repository-upload.html">Uploading Artifacts to the Central Repository</a></li><li><a href="./mini/guide-maven-evangelism.html">Improving the Repository</a></li></ul></div></div><div class="section"><h3>References<a name="References"></a></h3><ul><li><a href="../pom.html">POM Overview</a> (<a href="../ref/current/maven-model/maven.html">Technical Project Descriptor</a>)</li><li><a href="../settings.html">Settings Overview</a> (<a href="../ref/current/maven-settings/settings.html">Technical Settings Descriptor</a>)</li><li><a href="../plugins/index.html">Core Plug-ins List</a></li><li><a href="../developer
s/mojo-api-specification.html">Mojo API</a></li><li><a href="../glossary.html">Glossary</a></li><li><a href="./MavenQuickReferenceCard.pdf">Maven Quick Reference Card - PDF</a></li></ul></div><div class="section"><h3>Javadoc API<a name="Javadoc_API"></a></h3><p>Here is some useful Javadoc API links to the current version of Maven:</p><ul><li><a class="externalLink" href="http://maven.apache.org/ref/current/maven-artifact/apidocs/">Maven Artifact</a></li><li><a class="externalLink" href="http://maven.apache.org/shared/maven-reporting-api/apidocs/">Maven Reporting</a></li><li><a class="externalLink" href="http://maven.apache.org/ref/current/maven-plugin-api/apidocs/">Maven Plugin API</a></li><li><a class="externalLink" href="http://maven.apache.org/ref/current/maven-model/apidocs/">Maven Model</a></li><li><a class="externalLink" href="http://maven.apache.org/ref/current/maven-core/apidocs/">Maven Core</a></li><li><a class="externalLink" href="http://maven.apache.org/ref/curren
t/maven-settings/apidocs/">Maven Settings</a></li></ul><p>You could also browse the <a class="externalLink" href="http://maven.apache.org/ref/current/">full technical documentation references</a> of the current version of Maven.</p></div></div>
+ <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements. See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership. The ASF licenses this file --><!-- to you 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/referen
ces/apt-format.html --><div class="section">
+<h2>Documentation<a name="Documentation"></a></h2>
+<div class="section">
+<h3>Getting Started with Maven<a name="Getting_Started_with_Maven"></a></h3>
+<ul>
+<li><a href="./getting-started/maven-in-five-minutes.html">Getting Started in 5 Minutes</a></li>
+<li><a href="./getting-started/index.html">Getting Started in 30 Minutes</a></li></ul></div>
+<div class="section">
+<h3>Introductions<a name="Introductions"></a></h3>
+<ul>
+<li><a href="./introduction/introduction-to-the-lifecycle.html">The Build Lifecycle</a></li>
+<li><a href="./introduction/introduction-to-the-pom.html">The POM</a></li>
+<li><a href="./introduction/introduction-to-profiles.html">Profiles</a></li>
+<li><a href="./introduction/introduction-to-repositories.html">Repositories</a></li>
+<li><a href="./introduction/introduction-to-the-standard-directory-layout.html">Standard Directory Layout</a></li>
+<li><a href="./introduction/introduction-to-dependency-mechanism.html">The Dependency Mechanism</a></li>
+<li><a href="./introduction/introduction-to-optional-and-excludes-dependencies.html"> Optional Dependencies and Dependency Exclusions</a></li></ul>
+<div class="section">
+<h4>Plugins<a name="Plugins"></a></h4>
+<ul>
+<li><a href="./introduction/introduction-to-plugins.html">Plugin Development</a></li>
+<li><a href="./mini/guide-configuring-plugins.html">Configuring Plug-ins</a></li>
+<li><a href="./introduction/introduction-to-plugin-registry.html">The Plugin Registry</a></li>
+<li><a href="./introduction/introduction-to-plugin-prefix-mapping.html">Plugin Prefix Resolution</a></li>
+<li><a href="./introduction/introduction-to-plugin-resolution.html"> Introduction to Maven Plugin Resolution</a></li>
+<li><a href="./plugin/guide-ant-plugin-development.html">Developing Ant Plugins</a></li>
+<li><a href="./plugin/guide-java-plugin-development.html">Developing Java Plugins</a></li></ul></div>
+<div class="section">
+<h4>Site<a name="Site"></a></h4>
+<ul>
+<li><a href="./mini/guide-site.html">Creating a Site</a></li>
+<li><a class="externalLink" href="http://maven.apache.org/doxia/references/apt-format.html">The APT Format</a></li>
+<li><a href="./mini/guide-snippet-macro.html">Snippet Macro</a></li></ul></div>
+<div class="section">
+<h4>Archetypes<a name="Archetypes"></a></h4>
+<ul>
+<li><a href="./introduction/introduction-to-archetypes.html">What is an Archetype</a></li>
+<li><a href="./mini/guide-creating-archetypes.html">Creating Archetypes</a></li></ul></div>
+<div class="section">
+<h4>Upgrading<a name="Upgrading"></a></h4>
+<ul>
+<li><a href="./mini/guide-m1-m2.html">From Maven 1.x to Maven 2.x</a></li>
+<li><a href="./mini/guide-using-m1-repos-with-m2.html">Using Maven 1.x repositories with Maven 2.x</a></li>
+<li><a href="./mini/guide-relocation.html">Relocation of Artifacts</a></li></ul></div>
+<div class="section">
+<h4>Repositories<a name="Repositories"></a></h4>
+<ul>
+<li><a href="./mini/guide-3rd-party-jars-local.html">Installing 3rd party JARs to Local Repository</a></li>
+<li><a href="./mini/guide-3rd-party-jars-remote.html">Deploying 3rd party JARs to Remote Repository</a></li>
+<li><a href="./mini/guide-coping-with-sun-jars.html">Coping with Sun JARs</a></li>
+<li><a href="./mini/guide-repository-ssl.html">Remote repository access through authenticated HTTPS</a></li></ul><!-- * {{{./introduction/introduction-to-artifact-resolution.html}Repository Definitions and Artifact Resolution}} --></div></div>
+<div class="section">
+<h3>Guides<a name="Guides"></a></h3>
+<ul>
+<li><a href="./mini/guide-assemblies.html">Creating Assemblies</a></li>
+<li><a href="./mini/guide-archive-configuration.html">Configuring Archive Plugins</a></li>
+<li><a href="./mini/guide-configuring-maven.html">Configuring Maven</a></li>
+<li><a href="./mini/guide-mirror-settings.html">Mirror Settings</a></li>
+<li><a href="./mini/guide-deployment-security-settings.html">Deployment and Security Settings</a></li>
+<li><a href="./mini/guide-generating-sources.html">Generating Sources</a></li>
+<li><a href="./mini/guide-manifest.html">Working with Manifests</a></li>
+<li><a href="./mini/guide-maven-classloading.html">Maven Classloading</a></li>
+<li><a href="./mini/guide-multiple-modules.html">Using Multiple Modules in a Build</a></li>
+<li><a href="./mini/guide-multiple-repositories.html">Using Multiple Repositories</a></li>
+<li><a href="./mini/guide-proxies.html">Using Proxies</a></li>
+<li><a href="./mini/guide-releasing.html">Using the Release Plugin</a></li>
+<li><a href="./mini/guide-using-ant.html">Using Ant with Maven</a></li>
+<li><a href="./mini/guide-using-modello.html">Using Modello</a></li>
+<li><a href="./mini/guide-webapp.html">Webapps</a></li>
+<li><a href="./mini/guide-using-extensions.html">Using Extensions</a></li>
+<li><a href="./mini/guide-building-for-different-environments.html">Building For Different Environments with Maven 2</a></li>
+<li><a href="./mini/guide-using-toolchains.html">Using Toolchains</a></li>
+<li><a href="./mini/guide-encryption.html"> Encrypting passwords in settings.xml</a></li>
+<li><a href="./mini/guide-http-settings.html"> Guide to HTTP Connection Settings</a></li>
+<li><a href="./mini/guide-wagon-providers.html"> Guide to Selecting Alternative Wagon Providers</a></li>
+<li><a href="./mini/guide-building-jdk14-on-jdk15.html"> Guide to Building JDK 1.4 Projects Using JDK 1.5</a></li>
+<li><a href="./mini/guide-default-execution-ids.html"> Guide to Configuring Default Mojo Executions</a></li></ul><!-- ** Testing --><!-- * {{{./mini/guide-attached-tests.html}Reusable Test JARs}} -->
+<div class="section">
+<h4>Maven Tools and IDE Integration<a name="Maven_Tools_and_IDE_Integration"></a></h4>
+<ul>
+<li><a href="./mini/guide-ide-eclipse.html">Eclipse</a></li>
+<li><a href="./mini/guide-ide-idea.html">IDEA</a></li>
+<li><a href="./mini/guide-ide-netbeans/guide-ide-netbeans.html">NetBeans 4.0 (4.1 and 5.0)</a></li>
+<li><a href="./mini/guide-bash-m2-completion.html">Maven 2.x Auto-Completion Using BASH</a></li></ul></div></div>
+<div class="section">
+<h3>Development Guides<a name="Development_Guides"></a></h3>
+<ul>
+<li><a href="./development/guide-building-m2.html">Building Maven from Scratch</a></li>
+<li><a href="./development/guide-m2-development.html">Developing Maven</a></li>
+<li><a href="./development/guide-plugin-documentation.html">The Plugin Documentation Standard</a></li>
+<li><a href="./development/guide-documentation-style.html">Maven Documentation Style</a></li></ul></div>
+<div class="section">
+<h3>The Maven Community<a name="The_Maven_Community"></a></h3>
+<ul>
+<li><a href="../community.html">The Maven Community</a></li>
+<li><a href="./development/guide-helping.html">Helping with Maven</a></li>
+<li><a href="./mini/guide-new-committers.html">Guide for New Committers</a></li>
+<li><a href="./development/guide-testing-development-plugins.html">Testing Development Versions of Plugins</a></li>
+<li><a href="../articles.html">3rd Party Resources</a></li></ul>
+<div class="section">
+<h4>Conventions<a name="Conventions"></a></h4>
+<ul>
+<li><a href="../maven-conventions.html">Maven Conventions</a></li>
+<li><a href="./mini/guide-naming-conventions.html">Naming Conventions</a></li>
+<li><a href="./mini/guide-using-one-source-directory.html">When You Can't Use the Conventions</a></li></ul></div>
+<div class="section">
+<h4>The Central Repository<a name="The_Central_Repository"></a></h4>
+<ul>
+<li><a href="./mini/guide-central-repository-upload.html">Uploading Artifacts to the Central Repository</a></li>
+<li><a href="./mini/guide-maven-evangelism.html">Improving the Repository</a></li></ul></div></div>
+<div class="section">
+<h3>References<a name="References"></a></h3>
+<ul>
+<li><a href="../pom.html">POM Overview</a> (<a href="../ref/current/maven-model/maven.html">Technical Project Descriptor</a>)</li>
+<li><a href="../settings.html">Settings Overview</a> (<a href="../ref/current/maven-settings/settings.html">Technical Settings Descriptor</a>)</li>
+<li><a href="../plugins/index.html">Core Plug-ins List</a></li>
+<li><a href="../developers/mojo-api-specification.html">Mojo API</a></li>
+<li><a href="../glossary.html">Glossary</a></li>
+<li><a href="./MavenQuickReferenceCard.pdf">Maven Quick Reference Card - PDF</a></li></ul></div>
+<div class="section">
+<h3>Javadoc API<a name="Javadoc_API"></a></h3>
+<p>Here is some useful Javadoc API links to the current version of Maven:</p>
+<ul>
+<li><a class="externalLink" href="http://maven.apache.org/ref/current/maven-artifact/apidocs/">Maven Artifact</a></li>
+<li><a class="externalLink" href="http://maven.apache.org/shared/maven-reporting-api/apidocs/">Maven Reporting</a></li>
+<li><a class="externalLink" href="http://maven.apache.org/ref/current/maven-plugin-api/apidocs/">Maven Plugin API</a></li>
+<li><a class="externalLink" href="http://maven.apache.org/ref/current/maven-model/apidocs/">Maven Model</a></li>
+<li><a class="externalLink" href="http://maven.apache.org/ref/current/maven-core/apidocs/">Maven Core</a></li>
+<li><a class="externalLink" href="http://maven.apache.org/ref/current/maven-settings/apidocs/">Maven Settings</a></li></ul>
+<p>You could also browse the <a class="externalLink" href="http://maven.apache.org/ref/current/">full technical documentation references</a> of the current version of Maven.</p></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/guides/introduction/introduction-to-archetypes.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/introduction/introduction-to-archetypes.html (original)
+++ websites/staging/maven/trunk/content/guides/introduction/introduction-to-archetypes.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -14,7 +14,7 @@
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jason van Zyl" />
<meta name="Date-Creation-yyyymmdd" content="20090826" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -44,7 +44,7 @@
Introduction to Archetypes
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -232,7 +232,63 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Introduction to Archetypes<a name="Introduction_to_Archetypes"></a></h2></div><div class="section"><h2>What is Archetype?<a name="What_is_Archetype"></a></h2><p>In short, Archetype is a Maven project templating toolkit. An archetype is defined as <i>an original pattern or model from which all other things of the same kind are made</i>. The names fits as we are trying to provide a system that provides a consistent means of generating Maven projects. Archetype will help authors create Maven project templates for users, and provides users with the means to generate parameterized versions of those project templates.</p><p>Using archetypes provides a great way to enable developers quickly in a way consistent with best practices employed by your project or organization. Within the Maven project we use archetypes to try and get our users up and running as quickly as possible by providing a sample project that demonstrates many of the features of Mav
en while introducing new users to the best practices employed by Maven. In a matter of seconds a new user can have a working Maven project to use as a jumping board for investigating more of the features in Maven. We have also tried to make the Archetype mechanism additive and by that we mean allowing portions of a project to be captured in an archetype so that pieces or aspects of a project can be added to existing projects. A good example of this is the Maven site archetype. If, for example, you have used the quick start archetype to generate a working project you can then quickly create a site for that project by using the site archetype within that existing project. You can do anything like this with archetypes.</p><p>You may want to standardize J2EE development within your organization so you may want to provide archetypes for EJBs, or WARs, or for your web services. Once these archetypes are created and deployed in your organization's repository they are available for
use by all developers within your organization.</p><div class="section"><h3>Using an Archetype<a name="Using_an_Archetype"></a></h3><p>To create a new project based on an Archetype, you need to call <tt>mvn archetype:generate</tt> goal, like the following:</p><div class="source"><pre>mvn archetype:generate</pre></div><p>Please refer to <a class="externalLink" href="http://maven.apache.org/plugins/maven-archetype-plugin/usage.html">Archetype Plugin Page</a>.</p></div><div class="section"><h3>Provided Archetypes<a name="Provided_Archetypes"></a></h3><p>Maven provides several Archetype artifacts:</p><table border="1" class="bodyTable"><tr class="a"><th align="left">Archetype ArtifactIds</th><th align="left">Description</th></tr><tr class="b"><td align="left">maven-archetype-archetype</td><td align="left">An archetype which contains a sample archetype.</td></tr><tr class="a"><td align="left">maven-archetype-j2ee-simple</td><td align="left">An archetype which contains a simplifed
sample J2EE application.</td></tr><tr class="b"><td align="left">maven-archetype-mojo</td><td align="left">An archetype which contains a sample a sample Maven plugin.</td></tr><tr class="a"><td align="left">maven-archetype-plugin</td><td align="left">An archetype which contains a sample Maven plugin.</td></tr><tr class="b"><td align="left">maven-archetype-plugin-site</td><td align="left">An archetype which contains a sample Maven plugin site.</td></tr><tr class="a"><td align="left">maven-archetype-portlet</td><td align="left">An archetype which contains a sample JSR-268 Portlet.</td></tr><tr class="b"><td align="left">maven-archetype-quickstart</td><td align="left">An archetype which contains a sample Maven project.</td></tr><tr class="a"><td align="left">maven-archetype-simple</td><td align="left">An archetype which contains a simple Maven project.</td></tr><tr class="b"><td align="left">maven-archetype-site</td><td align="left">An archetype which contains a sample Maven s
ite which demonstrates some of the supported document types like APT, XDoc, and FML and demonstrates how to i18n your site.</td></tr><tr class="a"><td align="left">maven-archetype-site-simple</td><td align="left">An archetype which contains a sample Maven site.</td></tr><tr class="b"><td align="left">maven-archetype-webapp</td><td align="left">An archetype which contains a sample Maven Webapp project.</td></tr></table><p>For more information on these archetypes, please refer the <a class="externalLink" href="http://maven.apache.org/archetype/maven-archetype-bundles/">Maven Archetypes page</a>.</p></div><div class="section"><h3>What makes up an Archetype?<a name="What_makes_up_an_Archetype"></a></h3><p>Archetypes are packaged up in a JAR and they consist of the archetype metadata which describes the contents of archetype and a set of <a class="externalLink" href="http://velocity.apache.org/">Velocity</a> templates which make up the prototype project. If you would like to know
how to make your own archetypes please refer to our <a href="../mini/guide-creating-archetypes.html">Guide to creating archetypes</a>.</p></div></div>
+ <div class="section">
+<h2>Introduction to Archetypes<a name="Introduction_to_Archetypes"></a></h2></div>
+<div class="section">
+<h2>What is Archetype?<a name="What_is_Archetype"></a></h2>
+<p>In short, Archetype is a Maven project templating toolkit. An archetype is defined as <i>an original pattern or model from which all other things of the same kind are made</i>. The names fits as we are trying to provide a system that provides a consistent means of generating Maven projects. Archetype will help authors create Maven project templates for users, and provides users with the means to generate parameterized versions of those project templates.</p>
+<p>Using archetypes provides a great way to enable developers quickly in a way consistent with best practices employed by your project or organization. Within the Maven project we use archetypes to try and get our users up and running as quickly as possible by providing a sample project that demonstrates many of the features of Maven while introducing new users to the best practices employed by Maven. In a matter of seconds a new user can have a working Maven project to use as a jumping board for investigating more of the features in Maven. We have also tried to make the Archetype mechanism additive and by that we mean allowing portions of a project to be captured in an archetype so that pieces or aspects of a project can be added to existing projects. A good example of this is the Maven site archetype. If, for example, you have used the quick start archetype to generate a working project you can then quickly create a site for that project by using the site archetype within
that existing project. You can do anything like this with archetypes.</p>
+<p>You may want to standardize J2EE development within your organization so you may want to provide archetypes for EJBs, or WARs, or for your web services. Once these archetypes are created and deployed in your organization's repository they are available for use by all developers within your organization.</p>
+<div class="section">
+<h3>Using an Archetype<a name="Using_an_Archetype"></a></h3>
+<p>To create a new project based on an Archetype, you need to call <tt>mvn archetype:generate</tt> goal, like the following:</p>
+<div class="source">
+<pre>mvn archetype:generate</pre></div>
+<p>Please refer to <a class="externalLink" href="http://maven.apache.org/plugins/maven-archetype-plugin/usage.html">Archetype Plugin Page</a>.</p></div>
+<div class="section">
+<h3>Provided Archetypes<a name="Provided_Archetypes"></a></h3>
+<p>Maven provides several Archetype artifacts:</p>
+<table border="1" class="bodyTable">
+<tr class="a">
+<th align="left">Archetype ArtifactIds</th>
+<th align="left">Description</th></tr>
+<tr class="b">
+<td align="left">maven-archetype-archetype</td>
+<td align="left">An archetype which contains a sample archetype.</td></tr>
+<tr class="a">
+<td align="left">maven-archetype-j2ee-simple</td>
+<td align="left">An archetype which contains a simplifed sample J2EE application.</td></tr>
+<tr class="b">
+<td align="left">maven-archetype-mojo</td>
+<td align="left">An archetype which contains a sample a sample Maven plugin.</td></tr>
+<tr class="a">
+<td align="left">maven-archetype-plugin</td>
+<td align="left">An archetype which contains a sample Maven plugin.</td></tr>
+<tr class="b">
+<td align="left">maven-archetype-plugin-site</td>
+<td align="left">An archetype which contains a sample Maven plugin site.</td></tr>
+<tr class="a">
+<td align="left">maven-archetype-portlet</td>
+<td align="left">An archetype which contains a sample JSR-268 Portlet.</td></tr>
+<tr class="b">
+<td align="left">maven-archetype-quickstart</td>
+<td align="left">An archetype which contains a sample Maven project.</td></tr>
+<tr class="a">
+<td align="left">maven-archetype-simple</td>
+<td align="left">An archetype which contains a simple Maven project.</td></tr>
+<tr class="b">
+<td align="left">maven-archetype-site</td>
+<td align="left">An archetype which contains a sample Maven site which demonstrates some of the supported document types like APT, XDoc, and FML and demonstrates how to i18n your site.</td></tr>
+<tr class="a">
+<td align="left">maven-archetype-site-simple</td>
+<td align="left">An archetype which contains a sample Maven site.</td></tr>
+<tr class="b">
+<td align="left">maven-archetype-webapp</td>
+<td align="left">An archetype which contains a sample Maven Webapp project.</td></tr></table>
+<p>For more information on these archetypes, please refer the <a class="externalLink" href="http://maven.apache.org/archetype/maven-archetype-bundles/">Maven Archetypes page</a>.</p></div>
+<div class="section">
+<h3>What makes up an Archetype?<a name="What_makes_up_an_Archetype"></a></h3>
+<p>Archetypes are packaged up in a JAR and they consist of the archetype metadata which describes the contents of archetype and a set of <a class="externalLink" href="http://velocity.apache.org/">Velocity</a> templates which make up the prototype project. If you would like to know how to make your own archetypes please refer to our <a href="../mini/guide-creating-archetypes.html">Guide to creating archetypes</a>.</p></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/guides/introduction/introduction-to-artifact-resolution.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/introduction/introduction-to-artifact-resolution.html (original)
+++ websites/staging/maven/trunk/content/guides/introduction/introduction-to-artifact-resolution.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="John Casey" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Introduction to repository definitions and artifact resolution
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -231,7 +231,19 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Introduction to Repository definitions and artifact resolution<a name="Introduction_to_Repository_definitions_and_artifact_resolution"></a></h2><p>As you no doubt know by now, artifacts are a central concept to Maven. Since artifacts are referenced in abstract terms (groupId/artifactId rather than file path), they must be available in the Maven repository system in order for the build process to resolve them. This really amounts to putting the referenced artifacts into a Maven repository. </p><p>To promote flexibility in the configuration of your build environment, Maven allows multiple repositories to be defined from which artifacts can be resolved. Repositories are always defined in the POM, but since POMs can inherit from one another, and POM dependencies are resolved transitively, predicting which repository will be used to resolve a particular artifact can be daunting.</p><p>This document will attempt to explain the rules involved with c
onstructing repository lists for resolving artifacts referenced in various parts of the build process, and eliminate - or at least, reduce - the potential for confusion when it comes to artifact resolution.</p><div class="section"><h3>Goals<a name="Goals"></a></h3><p>The artifact resolution process in Maven has a couple of central goals which should help make the build process as flexible and powerful as possible. They are:</p><ul><li>Allow the local POM (the one being built) to have the first opportunity to control resolution.<p><i>NOTE: In the case of an inheritance hierarchy, the ancestor POMs are appended to the current repository list in inside-out order.</i></p></li><li>Allow the declaring-POM (the one declaring the dependency, in the case of transitivity) the second opportunity.</li><li>Default to the repositories defined in the super-POM for resolution.</li></ul><!-- Repository list construction (for resolution) --><!-- ~~Repository sources (local vs. default vs. inh
eritance vs. transitive POMs) --><!-- ~~Preserving the authority of the POM which declares the artifacts --><!-- ~~Local-wins priority (during inheritance AND transitive dependency resolution) --><!-- ~~Keeping the super-POM repositories last in line (ensuring their default status) --><!-- The net effect: a sample walkthrough --></div></div>
+ <div class="section">
+<h2>Introduction to Repository definitions and artifact resolution<a name="Introduction_to_Repository_definitions_and_artifact_resolution"></a></h2>
+<p>As you no doubt know by now, artifacts are a central concept to Maven. Since artifacts are referenced in abstract terms (groupId/artifactId rather than file path), they must be available in the Maven repository system in order for the build process to resolve them. This really amounts to putting the referenced artifacts into a Maven repository. </p>
+<p>To promote flexibility in the configuration of your build environment, Maven allows multiple repositories to be defined from which artifacts can be resolved. Repositories are always defined in the POM, but since POMs can inherit from one another, and POM dependencies are resolved transitively, predicting which repository will be used to resolve a particular artifact can be daunting.</p>
+<p>This document will attempt to explain the rules involved with constructing repository lists for resolving artifacts referenced in various parts of the build process, and eliminate - or at least, reduce - the potential for confusion when it comes to artifact resolution.</p>
+<div class="section">
+<h3>Goals<a name="Goals"></a></h3>
+<p>The artifact resolution process in Maven has a couple of central goals which should help make the build process as flexible and powerful as possible. They are:</p>
+<ul>
+<li>Allow the local POM (the one being built) to have the first opportunity to control resolution.
+<p><i>NOTE: In the case of an inheritance hierarchy, the ancestor POMs are appended to the current repository list in inside-out order.</i></p></li>
+<li>Allow the declaring-POM (the one declaring the dependency, in the case of transitivity) the second opportunity.</li>
+<li>Default to the repositories defined in the super-POM for resolution.</li></ul><!-- Repository list construction (for resolution) --><!-- ~~Repository sources (local vs. default vs. inheritance vs. transitive POMs) --><!-- ~~Preserving the authority of the POM which declares the artifacts --><!-- ~~Local-wins priority (during inheritance AND transitive dependency resolution) --><!-- ~~Keeping the super-POM repositories last in line (ensuring their default status) --><!-- The net effect: a sample walkthrough --></div></div>
</div>
</div>
<div class="clear">