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 [13/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/general.html
==============================================================================
--- websites/staging/maven/trunk/content/general.html (original)
+++ websites/staging/maven/trunk/content/general.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">
@@ -12,7 +12,7 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <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>
@@ -42,7 +42,7 @@
Frequently Asked Technical Questions
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -245,73 +245,137 @@
"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. --><div class="section"><h2><a name="top">Frequently Asked Technical Questions</a><a name="Frequently_Asked_Technical_Questions"></a></h2><ol style="list-style-type: decimal"><li><a href="#encoding-warning">How do I prevent "[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!"</a></li><li><a href="#scope-provided">How do I prevent including JARs in WEB-INF/lib? I need a "compile only" scope!</a></li><li><a href="#available-plugins">How do I list available plugins?</a></li><li><a href="#plugin-version">How do I determine what version of a plugin I am using?</a></li><li><a href="#using-ant-tasks">How can I use Ant tasks in a Maven build?</a></li><li><a href="#maven-ant-tasks">How can I use Maven features in an Ant build?</a></li><li><a href="#Compiling-J2SE-5">How do I set up Maven so it will compile with a target and source JVM of my choice?</a></li><li><a href="#dir-struct"
>Is it possible to create my own directory structure?</a></li><li><a href="#m2-source-code">Where is the source code? I couldn't seem to find a link anywhere on the Maven2 site.</a></li><li><a href="#proxy-needed">Maven can't seem to download the dependencies. Is my installation correct?</a></li><li><a href="#importing-jars">I have a jar that I want to put into my local repository. How can I copy it in?</a></li><li><a href="#unsubscribing-from-mailing-lists">How do I unsubscribe from Maven mailing lists?</a></li><li><a href="#skip-test">How do I skip the tests?</a></li><li><a href="#run-one-test">How can I run a single unit test?</a></li><li><a href="#special-characters-site">Handle special characters in site</a></li><li><a href="#tools-jar-dependency">How do I include <tt>tools.jar</tt> in my dependencies?</a></li><li><a href="#test-property-name">Maven compiles my test classes but doesn't run them?</a></li><li><a href="#snapshot-artifacts">Where are Maven SNAPSHOT artifact
s?</a></li><li><a href="#maven-xsd">Where are the Maven XSD schemas?</a></li><li><a href="#getting-help">Maven doesn't work, how do I get help?</a></li><li><a href="#How_to_produce_execution_debug_output_or_error_messages">How to produce execution debug output or error messages?</a></li><li><a href="#What_is_a_Mojo">What is a Mojo?</a></li><li><a href="#How_to_find_dependencies">How to find dependencies on public Maven repositories?</a></li></ol></div><dl><dt><a name="encoding-warning">How do I prevent "[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!"</a></dt><dd>
- <p>
+ under the License. --><div class="section">
+<h2><a name="top">Frequently Asked Technical Questions</a><a name="Frequently_Asked_Technical_Questions"></a></h2>
+<ol style="list-style-type: decimal">
+<li><a href="#encoding-warning">How do I prevent "[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!"</a></li>
+<li><a href="#scope-provided">How do I prevent including JARs in WEB-INF/lib? I need a "compile only" scope!</a></li>
+<li><a href="#available-plugins">How do I list available plugins?</a></li>
+<li><a href="#plugin-version">How do I determine what version of a plugin I am using?</a></li>
+<li><a href="#using-ant-tasks">How can I use Ant tasks in a Maven build?</a></li>
+<li><a href="#maven-ant-tasks">How can I use Maven features in an Ant build?</a></li>
+<li><a href="#Compiling-J2SE-5">How do I set up Maven so it will compile with a target and source JVM of my choice?</a></li>
+<li><a href="#dir-struct">Is it possible to create my own directory structure?</a></li>
+<li><a href="#m2-source-code">Where is the source code? I couldn't seem to find a link anywhere on the Maven2 site.</a></li>
+<li><a href="#proxy-needed">Maven can't seem to download the dependencies. Is my installation correct?</a></li>
+<li><a href="#importing-jars">I have a jar that I want to put into my local repository. How can I copy it in?</a></li>
+<li><a href="#unsubscribing-from-mailing-lists">How do I unsubscribe from Maven mailing lists?</a></li>
+<li><a href="#skip-test">How do I skip the tests?</a></li>
+<li><a href="#run-one-test">How can I run a single unit test?</a></li>
+<li><a href="#special-characters-site">Handle special characters in site</a></li>
+<li><a href="#tools-jar-dependency">How do I include <tt>tools.jar</tt> in my dependencies?</a></li>
+<li><a href="#test-property-name">Maven compiles my test classes but doesn't run them?</a></li>
+<li><a href="#snapshot-artifacts">Where are Maven SNAPSHOT artifacts?</a></li>
+<li><a href="#maven-xsd">Where are the Maven XSD schemas?</a></li>
+<li><a href="#getting-help">Maven doesn't work, how do I get help?</a></li>
+<li><a href="#How_to_produce_execution_debug_output_or_error_messages">How to produce execution debug output or error messages?</a></li>
+<li><a href="#What_is_a_Mojo">What is a Mojo?</a></li>
+<li><a href="#How_to_find_dependencies">How to find dependencies on public Maven repositories?</a></li></ol></div>
+<dl>
+<dt><a name="encoding-warning">How do I prevent "[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!"</a></dt>
+<dd>
+
+<p>
This or a similar warning is emitted by a plugin that processes plain text files but has not been configured to
use a specific file encoding. So eliminating the warning is simply a matter of finding out what plugin emits it
and how to configure the file encoding for it. For plugins that follow our guideline for
<a class="externalLink" href="http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding">source file encoding</a>,
this is as easy as adding the following property to your POM (or one of its parent POMs):
</p>
- <div class="source"><pre><project>
+
+<div class="source">
+<pre><project>
...
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
...
</project></pre></div>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="scope-provided">How do I prevent including JARs in WEB-INF/lib? I need a "compile only" scope!</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="scope-provided">How do I prevent including JARs in WEB-INF/lib? I need a "compile only" scope!</a></dt>
+<dd>
+
+<p>
The scope you should use for this is
<tt>provided</tt>. This indicates to Maven that the dependency will be
provided at run time by its container or the JDK, for example.
</p>
- <p>
+
+<p>
Dependencies with this scope will not be passed on transitively, nor will they be bundled in an package such
as a WAR, or included in the runtime classpath.
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="available-plugins">How do I list available plugins?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="available-plugins">How do I list available plugins?</a></dt>
+<dd>
+
+<p>
The "Available Plugins" page lists them and provides additional information.
See <a class="externalLink" href="http://maven.apache.org/plugins/">http://maven.apache.org/plugins</a>
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="plugin-version">How do I determine what version of a plugin I am using?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="plugin-version">How do I determine what version of a plugin I am using?</a></dt>
+<dd>
+
+<p>
You can use the <a href="/plugins/maven-help-plugin/">Maven Help Plugin</a>'s
<a href="/plugins/maven-help-plugin/describe-mojo.html"><tt>describe</tt></a> goal.
For example, to find out the version of the install plugin:
</p>
- <div class="source"><pre>mvn -Dplugin=install help:describe</pre></div>
- <p>
+
+<div class="source">
+<pre>mvn -Dplugin=install help:describe</pre></div>
+
+<p>
Note that you must give the plugin prefix as the argument to plugin, not it's artifact ID.
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="using-ant-tasks">How can I use Ant tasks in a Maven build?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="using-ant-tasks">How can I use Ant tasks in a Maven build?</a></dt>
+<dd>
+
+<p>
There are currently 2 alternatives:
</p>
- <ul>
- <li>
+
+<ul>
+
+<li>
For use in a plugin written in Java, Beanshell or other Java-like scripting language, you can construct
the Ant tasks using the
<a class="externalLink" href="http://ant.apache.org/manual/antexternal.html">instructions given in the Ant
documentation</a>
</li>
- <li>
+
+<li>
If you have very small amounts of Ant script specific to your project, you can use the
<a href="/plugins/maven-antrun-plugin/index.html">AntRun plugin</a>.
</li>
</ul>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="maven-ant-tasks">How can I use Maven features in an Ant build?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="maven-ant-tasks">How can I use Maven features in an Ant build?</a></dt>
+<dd>
+
+<p>
The <a href="/ant-tasks/index.html">Maven Ant Tasks</a> allow many of the features of
Maven, such as dependency management and repository deployment, to be used in an Ant build.
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="Compiling-J2SE-5">How do I set up Maven so it will compile with a target and source JVM of my choice?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="Compiling-J2SE-5">How do I set up Maven so it will compile with a target and source JVM of my choice?</a></dt>
+<dd>
+
+<p>
You must configure the source and target parameters in your pom. For example, to set the source and
target JVM to 1.5, you should have in your pom:
</p>
- <div class="source"><pre>
+
+<div class="source">
+<pre>
...
<build>
...
@@ -329,43 +393,65 @@
...
</build>
...</pre></div>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="dir-struct">Is it possible to create my own directory structure?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="dir-struct">Is it possible to create my own directory structure?</a></dt>
+<dd>
+
+<p>
Absolutely yes!
</p>
- <p>
+
+<p>
By configuring <sourceDirectory>, <resources> and other elements of
the <build> section.
</p>
- <p>
+
+<p>
In addition, you may need to change the plugin configuration if you are
not using plugin defaults for their files/directories.
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="m2-source-code">Where is the source code? I couldn't seem to find a link anywhere on the Maven2 site.</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="m2-source-code">Where is the source code? I couldn't seem to find a link anywhere on the Maven2 site.</a></dt>
+<dd>
+
+<p>
The source code can be found in <a href="source-repository.html">our subversion repository</a>.
</p>
- <p>
+
+<p>
For more information, see <a href="/guides/development/guide-building-m2.html">Building Maven 2.0</a>.
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="proxy-needed">Maven can't seem to download the dependencies. Is my installation correct?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="proxy-needed">Maven can't seem to download the dependencies. Is my installation correct?</a></dt>
+<dd>
+
+<p>
You most probably need to configure Maven to use a proxy. Please see the information on
<a href="/guides/mini/guide-proxies.html">Configuring a proxy</a> for information on how to configure your proxy
for Maven.
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="importing-jars">I have a jar that I want to put into my local repository. How can I copy it in?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="importing-jars">I have a jar that I want to put into my local repository. How can I copy it in?</a></dt>
+<dd>
+
+<p>
If you understand the layout of the Maven repository, you can copy the jar directly into where it
is meant to go. Maven will find this file next time it is run.
</p>
- <p>
+
+<p>
If you are not confident about the layout of the Maven repository, then you can
adapt the following command to load in your jar file, all on one line.
</p>
- <div class="source"><pre>
+
+<div class="source">
+<pre>
mvn install:install-file
-Dfile=<path-to-file>
-DgroupId=<group-id>
@@ -380,15 +466,23 @@ Where: <path-to-file> the path to
<version> the version of the file
<packaging> the packaging of the file e.g. jar
</pre></div>
- <p>
+
+<p>
This should load in the file into the Maven repository, renaming it as needed.
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="unsubscribing-from-mailing-lists">How do I unsubscribe from Maven mailing lists?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="unsubscribing-from-mailing-lists">How do I unsubscribe from Maven mailing lists?</a></dt>
+<dd>
+
+<p>
To unsubscribe from a Maven mailing list you simply send a message to
- </p><div class="source"><pre>[mailing-list]-unsubscribe@maven.apache.org</pre></div>
+ </p>
+<div class="source">
+<pre>[mailing-list]-unsubscribe@maven.apache.org</pre></div>
- <p>
+
+<p>
So, if you have subscribed to <tt>users@maven.apache.org</tt> then you would
send a message to <tt>users-unsubscribe@maven.apache.org</tt> in order to
get off the list.
@@ -397,25 +491,39 @@ Where: <path-to-file> the path to
same address when unsubscribing that you used to subscribe before
asking for help.
</p>
- <p>
+
+<p>
If you find you still cannot get off a list then
send a message to <tt>[mailing-list]-help@maven.apache.org</tt>. These
instructions are also appended to every message sent out on a maven mailing
list ...
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="skip-test">How do I skip the tests?</a></dt><dd>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="skip-test">How do I skip the tests?</a></dt>
+<dd>
Add the parameter <tt>-Dmaven.test.skip=true</tt> or <tt>-DskipTests=true</tt> in the command line,
depending on whether you want to skip test compilation and execution or only execution. See the example
<a href="/plugins/maven-surefire-plugin/examples/skipping-test.html">Skipping Tests</a>
in the Surefire Plugin's documentation for more details.
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="run-one-test">How can I run a single unit test?</a></dt><dd>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="run-one-test">How can I run a single unit test?</a></dt>
+<dd>
Use the parameter <tt>-Dtest=MyTest</tt> at the command line.
NB: do not specify the entire package (org.apache.x.y.MyTest)
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="special-characters-site">Handle special characters in site</a></dt><dd>
- <p>Configure your ide to use the correct encoding. With eclipse, add
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="special-characters-site">Handle special characters in site</a></dt>
+<dd>
+
+<p>Configure your ide to use the correct encoding. With eclipse, add
<tt>-Dfile.encoding=ISO-8859-1</tt> in eclipse.ini file</p>
- <p>Configure the output encoding in your pom
- </p><div class="source"><pre>
+
+<p>Configure the output encoding in your pom
+ </p>
+<div class="source">
+<pre>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
@@ -427,17 +535,24 @@ Where: <path-to-file> the path to
</plugin>
...</pre></div>
- <p>
+
+<p>
Configure the file encoding use by mvn.
add to MAVEN_OPTS the encoding (same as the ide).
This can be made with adding <tt>MAVEN_OPTS="-Dfile.encoding=ISO-8859-1"</tt> in $HOME/.profile
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="tools-jar-dependency">How do I include <tt>tools.jar</tt> in my dependencies?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="tools-jar-dependency">How do I include <tt>tools.jar</tt> in my dependencies?</a></dt>
+<dd>
+
+<p>
The following code includes <tt>tools.jar</tt> for JDKs on Windows, Linux and Solaris (it is already
included in the runtime for Mac OS X and some free JDKs).
</p>
- <div class="source"><pre>
+
+<div class="source">
+<pre>
...
<profiles>
<profile>
@@ -460,14 +575,20 @@ Where: <path-to-file> the path to
</profile>
</profiles>
...</pre></div>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="test-property-name">Maven compiles my test classes but doesn't run them?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="test-property-name">Maven compiles my test classes but doesn't run them?</a></dt>
+<dd>
+
+<p>
Tests are run by the surefire plugin. The surefire plugin can be configured to run certain test classes and
you may have unintentionally done so by specifying a value to ${test}.
Check your settings.xml and pom.xml for a property named "test" which would like this:
</p>
- <div class="source"><pre>
+
+<div class="source">
+<pre>
...
<properties>
<property>
@@ -476,35 +597,50 @@ Where: <path-to-file> the path to
</property>
</properties>
...</pre></div>
- <p>
+
+<p>
or
</p>
- <div class="source"><pre>
+
+<div class="source">
+<pre>
...
<properties>
<test>some-value</test>
</properties>
...</pre></div>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="snapshot-artifacts">Where are Maven SNAPSHOT artifacts?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="snapshot-artifacts">Where are Maven SNAPSHOT artifacts?</a></dt>
+<dd>
+
+<p>
If you are trying to build a development version of Maven or plugins,
you may need to access the maven snapshot repositories.
</p>
- <p>
+
+<p>
You need to update your settings.xml file using the
<a href="/guides/development/guide-testing-development-plugins.html">
Guide to Plugin Snapshot Repositories</a>
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="maven-xsd">Where are the Maven XSD schemas?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="maven-xsd">Where are the Maven XSD schemas?</a></dt>
+<dd>
+
+<p>
The Maven XSD is located <a href="/xsd/maven-4.0.0.xsd">here</a> and the Maven
Settings XSD is located <a href="/xsd/settings-1.0.0.xsd">here</a>.
</p>
- <p>
+
+<p>
Your favorite IDE probably supports XSD schema's for pom.xml and settings.xml editing. You need to
specify the following:
- </p><div class="source"><pre>
+ </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
@@ -512,7 +648,9 @@ Where: <path-to-file> the path to
...
</project></pre></div>
- <div class="source"><pre>
+
+<div class="source">
+<pre>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
@@ -520,35 +658,61 @@ Where: <path-to-file> the path to
...
</settings></pre></div>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="getting-help">Maven doesn't work, how do I get help?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="getting-help">Maven doesn't work, how do I get help?</a></dt>
+<dd>
+
+<p>
We have compiled a list of available resources on the
<a href="/users/getting-help.html">getting help page</a>
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="How_to_produce_execution_debug_output_or_error_messages">How to produce execution debug output or error messages?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="How_to_produce_execution_debug_output_or_error_messages">How to produce execution debug output or error messages?</a></dt>
+<dd>
+
+<p>
You could call Maven with <i>-X</i> parameter or <i>-e</i> parameter. For more information,
run:
- </p><div class="source"><pre>mvn --help</pre></div>
+ </p>
+<div class="source">
+<pre>mvn --help</pre></div>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="What_is_a_Mojo">What is a Mojo?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="What_is_a_Mojo">What is a Mojo?</a></dt>
+<dd>
+
+<p>
A mojo is a <b>M</b>aven plain <b>O</b>ld <b>J</b>ava <b>O</b>bject. Each mojo is an executable
<i>goal</i> in Maven, and a plugin is a distribution of one or more related mojos.
</p>
- <p align="right"><a href="#top">[top]</a></p><hr /></dd><dt><a name="How_to_find_dependencies">How to find dependencies on public Maven repositories?</a></dt><dd>
- <p>
+
+<p align="right"><a href="#top">[top]</a></p><hr /></dd>
+<dt><a name="How_to_find_dependencies">How to find dependencies on public Maven repositories?</a></dt>
+<dd>
+
+<p>
You could use the following search engines:
</p>
- <ul>
- <li><a class="externalLink" href="http://search.maven.org/">http://search.maven.org</a></li>
- <li><a class="externalLink" href="http://repository.apache.org">http://repository.apache.org</a></li>
- <li><a class="externalLink" href="http://www.artifact-repository.org/">http://www.artifact-repository.org</a></li>
- <li><a class="externalLink" href="http://mvnrepository.com">http://mvnrepository.com</a></li>
- <li><a class="externalLink" href="http://www.mvnbrowser.com">http://www.mvnbrowser.com</a></li>
- <li><a class="externalLink" href="http://www.jarvana.com">http://www.jarvana.com</a></li>
+
+<ul>
+
+<li><a class="externalLink" href="http://search.maven.org/">http://search.maven.org</a></li>
+
+<li><a class="externalLink" href="http://repository.apache.org">http://repository.apache.org</a></li>
+
+<li><a class="externalLink" href="http://www.artifact-repository.org/">http://www.artifact-repository.org</a></li>
+
+<li><a class="externalLink" href="http://mvnrepository.com">http://mvnrepository.com</a></li>
+
+<li><a class="externalLink" href="http://www.mvnbrowser.com">http://www.mvnbrowser.com</a></li>
+
+<li><a class="externalLink" href="http://www.jarvana.com">http://www.jarvana.com</a></li>
</ul>
- <p align="right"><a href="#top">[top]</a></p></dd></dl>
+
+<p align="right"><a href="#top">[top]</a></p></dd></dl>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/glossary.html
==============================================================================
--- websites/staging/maven/trunk/content/glossary.html (original)
+++ websites/staging/maven/trunk/content/glossary.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="Jason van Zyl" />
- <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 Getting Started Guide
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -231,7 +231,26 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Glossary<a name="Glossary"></a></h2><p>This document describes some of the most common terms encountered while using Maven. These terms, that have an explicit meaning for Maven, can sometimes be confusing for newcomers.</p><ul><li><a name="Project"><b>Project</b></a>: Maven thinks in terms of projects. Everything that you will build are projects. Those projects follow a well defined "Project Object Model". Projects can depend on other projects, in which case the latter are called "dependencies". A project may consistent of several subprojects, however these subprojects are still treated equally as projects.</li><li><a name="Project_Object_Model_POM"><b>Project Object Model (POM)</b></a>: The Project Object Model, almost always referred as the POM for brevity, is the metadata that Maven needs to work with your project. Its name is "project.xml" and it is located in the root directory of each project.</li><li><a na
me="Artifact"><b>Artifact</b></a>: An artifact is something that is either produced or used by a project. Examples of artifacts produced by Maven for a project include: JARs, source and binary distributions, WARs. Each artifact is uniquely identified by a <a href="#GroupId">group id</a> and an artifact ID which is unique within a group.</li><li><a name="GroupId"><b>GroupId</b></a>: A group ID is a universally unique identifier for a project. While this is often just the project name (eg. <tt>commons-collections</tt>), it is helpful to use a fully-qualified package name to distinguish it from other projects with a similar name (eg. <tt>org.apache.maven</tt>).</li><li><a name="Dependency"><b>Dependency</b></a>: A typical Java project relies on libraries to build and/or run. Those are called "dependencies" inside Maven. Those dependencies are usually other projects' JAR artifacts, but are referenced by the POM that describes them.</li><li><a name="Plug-in"><b>Plug-in<
/b></a>: Maven is organized in plugins. Every piece of functionality in Maven is provided by a plugin. Plugins provide goals and use the metadata found in the POM to perform their task. 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.</li><li><a name="Mojo"><b>Mojo</b></a>: 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.</li></ul><!-- * {<<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. --><!-- Each goal exists in a plugin (except for those that you define yourself), and the --><!-- goal name usually reflects the plugin (eg. <<<java:compile>>> comes from the --><!-- <<<java>>> pl
ugin). --><ul><li><a name="Repository"><b>Repository</b></a>:<p>Refer to <a href="./guides/introduction/introduction-to-repositories.html">Introduction to Repositories</a></p></li><li><a name="Snapshots"><b>Snapshots</b></a>: Projects can (and should) have a special version including <tt>SNAPSHOT</tt> to indicate that they are a "work in progress", and are not yet released. When a snapshot dependency is encountered, it is always looked for in all remote repositories, and downloaded again if newer than the local copy.<p>The version can either be the string <tt>SNAPSHOT</tt> itself, indicating "the very latest" development version, or something like <tt>1.1-SNAPSHOT</tt>, indicating development that will be released as 1.1 (i.e. newer than 1.0, but not yet 1.1).</p></li><li><a name="APT"><b>APT</b></a>: APT is a wiki-like format of documentation that Maven currently understands.<p>For information on how to create APT files, refer to the <a href="./guides/mi
ni/guide-site.html">Guide to creating a site</a> document.</p></li><li><a name="XDoc"><b>XDoc</b></a>: XDoc is the format of documentation that Maven currently understands. It is quite simple, and allows embedding XHTML within a simple layout that is transformed into a uniform site.<p>For information on how to create XDoc files, refer to the <a href="./guides/mini/guide-site.html">Guide to creating a site</a> document.</p></li></ul></div>
+ <div class="section">
+<h2>Glossary<a name="Glossary"></a></h2>
+<p>This document describes some of the most common terms encountered while using Maven. These terms, that have an explicit meaning for Maven, can sometimes be confusing for newcomers.</p>
+<ul>
+<li><a name="Project"><b>Project</b></a>: Maven thinks in terms of projects. Everything that you will build are projects. Those projects follow a well defined "Project Object Model". Projects can depend on other projects, in which case the latter are called "dependencies". A project may consistent of several subprojects, however these subprojects are still treated equally as projects.</li>
+<li><a name="Project_Object_Model_POM"><b>Project Object Model (POM)</b></a>: The Project Object Model, almost always referred as the POM for brevity, is the metadata that Maven needs to work with your project. Its name is "project.xml" and it is located in the root directory of each project.</li>
+<li><a name="Artifact"><b>Artifact</b></a>: An artifact is something that is either produced or used by a project. Examples of artifacts produced by Maven for a project include: JARs, source and binary distributions, WARs. Each artifact is uniquely identified by a <a href="#GroupId">group id</a> and an artifact ID which is unique within a group.</li>
+<li><a name="GroupId"><b>GroupId</b></a>: A group ID is a universally unique identifier for a project. While this is often just the project name (eg. <tt>commons-collections</tt>), it is helpful to use a fully-qualified package name to distinguish it from other projects with a similar name (eg. <tt>org.apache.maven</tt>).</li>
+<li><a name="Dependency"><b>Dependency</b></a>: A typical Java project relies on libraries to build and/or run. Those are called "dependencies" inside Maven. Those dependencies are usually other projects' JAR artifacts, but are referenced by the POM that describes them.</li>
+<li><a name="Plug-in"><b>Plug-in</b></a>: Maven is organized in plugins. Every piece of functionality in Maven is provided by a plugin. Plugins provide goals and use the metadata found in the POM to perform their task. 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.</li>
+<li><a name="Mojo"><b>Mojo</b></a>: 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.</li></ul><!-- * {<<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. --><!-- Each goal exists in a plugin (except for those that you define yourself), and the --><!-- goal name usually reflects the plugin (eg. <<<java:compile>>> comes from the --><!-- <<<java>>> plugin). -->
+<ul>
+<li><a name="Repository"><b>Repository</b></a>:
+<p>Refer to <a href="./guides/introduction/introduction-to-repositories.html">Introduction to Repositories</a></p></li>
+<li><a name="Snapshots"><b>Snapshots</b></a>: Projects can (and should) have a special version including <tt>SNAPSHOT</tt> to indicate that they are a "work in progress", and are not yet released. When a snapshot dependency is encountered, it is always looked for in all remote repositories, and downloaded again if newer than the local copy.
+<p>The version can either be the string <tt>SNAPSHOT</tt> itself, indicating "the very latest" development version, or something like <tt>1.1-SNAPSHOT</tt>, indicating development that will be released as 1.1 (i.e. newer than 1.0, but not yet 1.1).</p></li>
+<li><a name="APT"><b>APT</b></a>: APT is a wiki-like format of documentation that Maven currently understands.
+<p>For information on how to create APT files, refer to the <a href="./guides/mini/guide-site.html">Guide to creating a site</a> document.</p></li>
+<li><a name="XDoc"><b>XDoc</b></a>: XDoc is the format of documentation that Maven currently understands. It is quite simple, and allows embedding XHTML within a simple layout that is transformed into a uniform site.
+<p>For information on how to create XDoc files, refer to the <a href="./guides/mini/guide-site.html">Guide to creating a site</a> document.</p></li></ul></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/guides/development/guide-building-m2.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/development/guide-building-m2.html (original)
+++ websites/staging/maven/trunk/content/guides/development/guide-building-m2.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="Brett Porter
Jason van Zyl" />
<meta name="Date-Creation-yyyymmdd" content="20121220" />
- <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 @@ Jason van Zyl" />
Guide to Building Maven
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -233,9 +233,84 @@ Jason van Zyl" />
</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>Building Maven<a name="Building_Maven"></a></h2><div class="section"><h3>Why would I want to build Maven?<a name="Why_would_I_want_to_build_Maven"></a></h3><p>Building Maven yourself is for one of two reasons:</p><ul><li>to try out a bleeding edge feature or bugfix (issues can be found in <a class="externalLink" href="http://jira.codehaus.org/browse/MNG"> JIRA</a>),</li><li>to fix a problem you are having and submit a patch to the developers team.</li></ul><p>Note, that you don't need to bootstrap Maven for day to day use, or to develop plugins. While we encourage getting involved and fixing bugs that you find, for day to day use we recommend using the latest release.</p></div><div class="section"><h3>Checking out the sources<a name="Checking_out_the_sources"></a></h3><p>All of the source code for Maven and its related libraries is in managed in the ASF source code repositories. Current development of the core of Maven, and som
e other components, are in git. Other pieces (and older versions) are in Subversion. For details, see <a class="externalLink" href="http://maven.apache.org/source-repository.html">http://maven.apache.org/source-repository.html</a>.</p><p>To build Maven 3 (the current stable branch), you need the <tt>trunk</tt> of the <tt>maven-3</tt> module. To check that out, run the command:</p><div><pre>git clone https://git-wip-us.apache.org/repos/asf/maven.git maven</pre></div><p>To build Maven 2, you need the <tt>maven-2.2.x</tt> branch . To check that out, run the command:</p><div><pre>git checkout maven-2.2.x</pre></div><div class="section"><h4>Other Modules<a name="Other_Modules"></a></h4><p>Other modules you might be interested in related to Maven development are:</p><ul><li><tt>core-integration-testing/trunk</tt> - git clone https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git</li><li><tt>plugins/trunk</tt> - The sources of the <a href="/plugins/">Maven plugins</a
>. These can be individually installed, or built together.</li><li><tt>plugin-tools/trunk</tt> - <a href="/plugin-tools/">Set of tools for Maven plugins</a> like test harness.</li><li><tt>release/trunk</tt> - Release manager and plugin.</li><li><tt>site/trunk</tt> - The Maven website.</li><li><tt>skins/trunk</tt> - <a href="/skins/">Skins</a> for generated site used by site plugin.</li><li>Some Maven sub projects<ul><li><tt>wagon</tt> - <a href="/wagon/">Maven Wagon</a>, used by the artifact code and others for providing the transport layer to get and put artifacts in a repository. git clone https://git-wip-us.apache.org/repos/asf/maven-wagon.git</li><li><tt>scm</tt> - <a href="/scm/">Maven SCM</a>, a generic API to communicate with various different SCM providers, used by Continuum and the release and SCM plugins. git clone https://git-wip-us.apache.org/repos/asf/maven-scm.git</li><li><tt>doxia/trunk</tt> - The <a href="/doxia/">Doxia</a> site generation library used by sev
eral report plugins and site plugin.</li><li><tt>surefire/trunk</tt> - The <a href="/surefire/">Surefire</a> test runner. git clone https://git-wip-us.apache.org/repos/asf/maven-surefire.git</li></ul></li><li><tt>shared/trunk</tt> - <a href="/shared/">Collection of shared libraries</a> like file/path handling.</li><li><tt>sandbox/trunk</tt> - Sandbox codes.</li><li><a class="externalLink" href="http://svn.plexus.codehaus.org/plexus/"> Plexus</a> - the IoC container used by Maven.</li></ul><p>If you're <a class="externalLink" href="http://svn.apache.org/viewvc/maven/trunks/">looking at the <tt>trunks</tt> directory with ViewVC</a>, there is seemingly nothing there. We use <a class="externalLink" href="http://svnbook.red-bean.com/en/1.0/ch07s03.html">externals definitions</a> to link together all the trunks into one logical location for convenience. If you want to see what is being linked into one logical location you can use the following command:</p><div><pre>svn propget svn
:externals</pre></div></div></div><div class="section"><h3>Building Maven<a name="Building_Maven"></a></h3><div class="section"><h4>Building Maven With Maven Installed<a name="Building_Maven_With_Maven_Installed"></a></h4><p>If you already have Maven installed, it can be faster to build a new version with Maven, rather than a clean bootstrap.</p><p>To do this, run from the <tt>maven-3</tt> or <tt>maven-2.2.x</tt> directory:</p><div><pre>mvn install</pre></div><p>Optionally, you can use the following to run the full (long) suite of integration tests; see below.</p><p>The assemblies will be created in <tt>apache-maven/target</tt> for Maven 2.0.x or <tt>maven-distribution</tt> for Maven 2.1, and can be unzipped to the location where you'd like Maven installed.</p></div><div class="section"><h4>Running the full integration tests<a name="Running_the_full_integration_tests"></a></h4><p>Before checking in a change or submitting a patch, it's a good idea to run the integration tests
. These live in their own directory in subversion, as noted above: <tt>core-integration-testing/trunk</tt>. Using your local build of Maven, run:</p><div><pre>mvn install -Prun-its</pre></div></div><div class="section"><h4>Building Maven Without Maven Installed<a name="Building_Maven_Without_Maven_Installed"></a></h4><p>If you do not have Maven installed, you can use <a class="externalLink" href="http://ant.apache.org">Apache Ant</a> to build Maven.</p><p>Once you have checked out the code, change into the <tt>maven-3</tt> or <tt>maven-2.2.x</tt> directory that was created.</p><p>Set the M2_HOME environment variable to the location that should contain Maven. This directory <b>must</b> be named after the Maven version you want to build and install, for example <tt>/usr/local/maven-2.2-SNAPSHOT</tt>.</p><div><pre>export M2_HOME=/usr/local/maven-2.2-SNAPSHOT
-PATH=$M2_HOME/bin:$PATH</pre></div><p>or</p><div><pre>set M2_HOME=c:\maven-2.2-SNAPSHOT
-set PATH=%M2_HOME%\bin;%PATH%</pre></div><p>From this, run the <tt>ant</tt> command:</p><div><pre>ant</pre></div><p>This will download dependencies, build Maven, and install it into the directory you specified as <tt>M2_HOME</tt> above.</p><p>If you have any problems or get any failures during the run, please report them to the <a href="../../mail-lists.html"> Maven Developers List</a>.</p><p>For more information, consult the project help in the Ant build file.</p><div><pre>ant -projecthelp</pre></div><p>The result is included here for convenience:</p><div class="source"><pre>Buildfile: build.xml
+ <!-- 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>Building Maven<a name="Building_Maven"></a></h2>
+<div class="section">
+<h3>Why would I want to build Maven?<a name="Why_would_I_want_to_build_Maven"></a></h3>
+<p>Building Maven yourself is for one of two reasons:</p>
+<ul>
+<li>to try out a bleeding edge feature or bugfix (issues can be found in <a class="externalLink" href="http://jira.codehaus.org/browse/MNG"> JIRA</a>),</li>
+<li>to fix a problem you are having and submit a patch to the developers team.</li></ul>
+<p>Note, that you don't need to bootstrap Maven for day to day use, or to develop plugins. While we encourage getting involved and fixing bugs that you find, for day to day use we recommend using the latest release.</p></div>
+<div class="section">
+<h3>Checking out the sources<a name="Checking_out_the_sources"></a></h3>
+<p>All of the source code for Maven and its related libraries is in managed in the ASF source code repositories. Current development of the core of Maven, and some other components, are in git. Other pieces (and older versions) are in Subversion. For details, see <a class="externalLink" href="http://maven.apache.org/source-repository.html">http://maven.apache.org/source-repository.html</a>.</p>
+<p>To build Maven 3 (the current stable branch), you need the <tt>trunk</tt> of the <tt>maven-3</tt> module. To check that out, run the command:</p>
+<div>
+<pre>git clone https://git-wip-us.apache.org/repos/asf/maven.git maven</pre></div>
+<p>To build Maven 2, you need the <tt>maven-2.2.x</tt> branch . To check that out, run the command:</p>
+<div>
+<pre>git checkout maven-2.2.x</pre></div>
+<div class="section">
+<h4>Other Modules<a name="Other_Modules"></a></h4>
+<p>Other modules you might be interested in related to Maven development are:</p>
+<ul>
+<li><tt>core-integration-testing/trunk</tt> - git clone https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git</li>
+<li><tt>plugins/trunk</tt> - The sources of the <a href="/plugins/">Maven plugins</a>. These can be individually installed, or built together.</li>
+<li><tt>plugin-tools/trunk</tt> - <a href="/plugin-tools/">Set of tools for Maven plugins</a> like test harness.</li>
+<li><tt>release/trunk</tt> - Release manager and plugin.</li>
+<li><tt>site/trunk</tt> - The Maven website.</li>
+<li><tt>skins/trunk</tt> - <a href="/skins/">Skins</a> for generated site used by site plugin.</li>
+<li>Some Maven sub projects
+<ul>
+<li><tt>wagon</tt> - <a href="/wagon/">Maven Wagon</a>, used by the artifact code and others for providing the transport layer to get and put artifacts in a repository. git clone https://git-wip-us.apache.org/repos/asf/maven-wagon.git</li>
+<li><tt>scm</tt> - <a href="/scm/">Maven SCM</a>, a generic API to communicate with various different SCM providers, used by Continuum and the release and SCM plugins. git clone https://git-wip-us.apache.org/repos/asf/maven-scm.git</li>
+<li><tt>doxia/trunk</tt> - The <a href="/doxia/">Doxia</a> site generation library used by several report plugins and site plugin.</li>
+<li><tt>surefire/trunk</tt> - The <a href="/surefire/">Surefire</a> test runner. git clone https://git-wip-us.apache.org/repos/asf/maven-surefire.git</li></ul></li>
+<li><tt>shared/trunk</tt> - <a href="/shared/">Collection of shared libraries</a> like file/path handling.</li>
+<li><tt>sandbox/trunk</tt> - Sandbox codes.</li>
+<li><a class="externalLink" href="http://svn.plexus.codehaus.org/plexus/"> Plexus</a> - the IoC container used by Maven.</li></ul>
+<p>If you're <a class="externalLink" href="http://svn.apache.org/viewvc/maven/trunks/">looking at the <tt>trunks</tt> directory with ViewVC</a>, there is seemingly nothing there. We use <a class="externalLink" href="http://svnbook.red-bean.com/en/1.0/ch07s03.html">externals definitions</a> to link together all the trunks into one logical location for convenience. If you want to see what is being linked into one logical location you can use the following command:</p>
+<div>
+<pre>svn propget svn:externals</pre></div></div></div>
+<div class="section">
+<h3>Building Maven<a name="Building_Maven"></a></h3>
+<div class="section">
+<h4>Building Maven With Maven Installed<a name="Building_Maven_With_Maven_Installed"></a></h4>
+<p>If you already have Maven installed, it can be faster to build a new version with Maven, rather than a clean bootstrap.</p>
+<p>To do this, run from the <tt>maven-3</tt> or <tt>maven-2.2.x</tt> directory:</p>
+<div>
+<pre>mvn install</pre></div>
+<p>Optionally, you can use the following to run the full (long) suite of integration tests; see below.</p>
+<p>The assemblies will be created in <tt>apache-maven/target</tt> for Maven 2.0.x or <tt>maven-distribution</tt> for Maven 2.1, and can be unzipped to the location where you'd like Maven installed.</p></div>
+<div class="section">
+<h4>Running the full integration tests<a name="Running_the_full_integration_tests"></a></h4>
+<p>Before checking in a change or submitting a patch, it's a good idea to run the integration tests. These live in their own directory in subversion, as noted above: <tt>core-integration-testing/trunk</tt>. Using your local build of Maven, run:</p>
+<div>
+<pre>mvn install -Prun-its</pre></div></div>
+<div class="section">
+<h4>Building Maven Without Maven Installed<a name="Building_Maven_Without_Maven_Installed"></a></h4>
+<p>If you do not have Maven installed, you can use <a class="externalLink" href="http://ant.apache.org">Apache Ant</a> to build Maven.</p>
+<p>Once you have checked out the code, change into the <tt>maven-3</tt> or <tt>maven-2.2.x</tt> directory that was created.</p>
+<p>Set the M2_HOME environment variable to the location that should contain Maven. This directory <b>must</b> be named after the Maven version you want to build and install, for example <tt>/usr/local/maven-2.2-SNAPSHOT</tt>.</p>
+<div>
+<pre>export M2_HOME=/usr/local/maven-2.2-SNAPSHOT
+PATH=$M2_HOME/bin:$PATH</pre></div>
+<p>or</p>
+<div>
+<pre>set M2_HOME=c:\maven-2.2-SNAPSHOT
+set PATH=%M2_HOME%\bin;%PATH%</pre></div>
+<p>From this, run the <tt>ant</tt> command:</p>
+<div>
+<pre>ant</pre></div>
+<p>This will download dependencies, build Maven, and install it into the directory you specified as <tt>M2_HOME</tt> above.</p>
+<p>If you have any problems or get any failures during the run, please report them to the <a href="../../mail-lists.html"> Maven Developers List</a>.</p>
+<p>For more information, consult the project help in the Ant build file.</p>
+<div>
+<pre>ant -projecthelp</pre></div>
+<p>The result is included here for convenience:</p>
+<div class="source">
+<pre>Buildfile: build.xml
The first time you build Maven from source, you have to build Maven without
Maven. This Ant script builds a minimal Maven, just enough to re-launch
Modified: websites/staging/maven/trunk/content/guides/development/guide-documentation-style.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/development/guide-documentation-style.html (original)
+++ websites/staging/maven/trunk/content/guides/development/guide-documentation-style.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="Dennis Lundberg" />
<meta name="Date-Creation-yyyymmdd" content="20080712" />
- <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 @@
Guide To Maven Documentation Style
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -232,13 +232,43 @@
</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>Guide To Maven Documentation Style<a name="Guide_To_Maven_Documentation_Style"></a></h2><div class="section"><h3>Where did the style came from?<a name="Where_did_the_style_came_from"></a></h3><p>The documentation style guide was created to make our documentation more consistent and also to apply best practices to the documentation as well. The standard has just been started and will expand over time based on the suggestions made on the Maven dev mailing list. It is a community consensus of how we should write our documentation.</p><p>Each rule in this guide should come with a motivation as to why it exists. References to external sources are encouraged.</p></div><div class="section"><h3>Date format<a name="Date_format"></a></h3><p>How people format a date varies around the world, sometimes making it hard for people to understand each other. The solution to this problem comes in the form of the ISO-8601 standard.</p><p>A date in
our documentation must follow this standard:</p><p><b>YYYY-MM-DD</b></p><p>where <b>YYYY</b> is the year in the Gregorian calendar, <b>MM</b> is the month of the year between 01 (January) and 12 (December), and <b>DD</b> is the day of the month between 01 and 31.</p><p><b>Note</b>: All documentation meta-data should respect this convention, for instance for this given APT document:</p><div class="source"><pre> ------
+ <!-- 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>Guide To Maven Documentation Style<a name="Guide_To_Maven_Documentation_Style"></a></h2>
+<div class="section">
+<h3>Where did the style came from?<a name="Where_did_the_style_came_from"></a></h3>
+<p>The documentation style guide was created to make our documentation more consistent and also to apply best practices to the documentation as well. The standard has just been started and will expand over time based on the suggestions made on the Maven dev mailing list. It is a community consensus of how we should write our documentation.</p>
+<p>Each rule in this guide should come with a motivation as to why it exists. References to external sources are encouraged.</p></div>
+<div class="section">
+<h3>Date format<a name="Date_format"></a></h3>
+<p>How people format a date varies around the world, sometimes making it hard for people to understand each other. The solution to this problem comes in the form of the ISO-8601 standard.</p>
+<p>A date in our documentation must follow this standard:</p>
+<p><b>YYYY-MM-DD</b></p>
+<p>where <b>YYYY</b> is the year in the Gregorian calendar, <b>MM</b> is the month of the year between 01 (January) and 12 (December), and <b>DD</b> is the day of the month between 01 and 31.</p>
+<p><b>Note</b>: All documentation meta-data should respect this convention, for instance for this given APT document:</p>
+<div class="source">
+<pre> ------
Guide To Maven Documentation Style
------
Dennis Lundberg
------
2008-07-03
- ------</pre></div><div class="section"><h4>References<a name="References"></a></h4><ul><li><a class="externalLink" href="http://www.w3.org/QA/Tips/iso-date">W3C Quality Web Tips</a></li><li><a class="externalLink" href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=26780">ISO-8601</a></li><li><a class="externalLink" href="http://en.wikipedia.org/wiki/ISO_8601">Wikipedia</a></li></ul><!-- NOTE: Add more rules here. Follow the heading style of the rule above. --></div></div><div class="section"><h3>POM Snippet<a name="POM_Snippet"></a></h3><p>A POM file must use 2 spaces for each indentation. Because POM snippets are often used in documentation to show the user how to configure something, it is important that these snippets aren't too wide. If the are too wide it will make the page difficult to read on a smaller screen.</p><p>When you use a snippet of XML from the POM as an example in your documentation, you need to make sure that the example
is properly indented. A user should be able to copy and paste the example into their own POM without the need to change the indentation afterwards.</p><p>Also, you should declare all parent POM elements to improve the comprehension. You could use ellipsis (i.e. ...) if you don't want to specify elements.</p><div class="section"><h4>Example<a name="Example"></a></h4><p>The following is an example of how the distribution management of the Maven site is configured.</p><div class="source"><pre><project>
+ ------</pre></div>
+<div class="section">
+<h4>References<a name="References"></a></h4>
+<ul>
+<li><a class="externalLink" href="http://www.w3.org/QA/Tips/iso-date">W3C Quality Web Tips</a></li>
+<li><a class="externalLink" href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=26780">ISO-8601</a></li>
+<li><a class="externalLink" href="http://en.wikipedia.org/wiki/ISO_8601">Wikipedia</a></li></ul><!-- NOTE: Add more rules here. Follow the heading style of the rule above. --></div></div>
+<div class="section">
+<h3>POM Snippet<a name="POM_Snippet"></a></h3>
+<p>A POM file must use 2 spaces for each indentation. Because POM snippets are often used in documentation to show the user how to configure something, it is important that these snippets aren't too wide. If the are too wide it will make the page difficult to read on a smaller screen.</p>
+<p>When you use a snippet of XML from the POM as an example in your documentation, you need to make sure that the example is properly indented. A user should be able to copy and paste the example into their own POM without the need to change the indentation afterwards.</p>
+<p>Also, you should declare all parent POM elements to improve the comprehension. You could use ellipsis (i.e. ...) if you don't want to specify elements.</p>
+<div class="section">
+<h4>Example<a name="Example"></a></h4>
+<p>The following is an example of how the distribution management of the Maven site is configured.</p>
+<div class="source">
+<pre><project>
...
<distributionManagement>
<site>
@@ -247,7 +277,22 @@
</site>
</distributionManagement>
...
-</project></pre></div><p>As you can see above the <tt><distributionManagement></tt> element is indented once (=2 spaces), the <tt><site></tt> element in indented twice (=4 spaces) and the <tt><id></tt> is indented three times (=6 spaces).</p></div></div><div class="section"><h3>Naming Documentation Files<a name="Naming_Documentation_Files"></a></h3><p>All file names should replace space by a minus (-), for instance for this given APT document:</p><div class="source"><pre> guide-documentation-style.apt</pre></div></div><div class="section"><h3>Updating Documentation Files<a name="Updating_Documentation_Files"></a></h3><p>A good practice is to update the date (with the correct date format) when you are updating documentation files.</p></div><div class="section"><h3>Write Thinking<a name="Write_Thinking"></a></h3><p>Here are some pointers about English rules when typing material:</p><ul><li><a class="externalLink" href="http://en.wikipedia.org/wiki/Wikip
edia:Manual_of_Style">Wikipedia:Manual of Style</a>, specifically <a class="externalLink" href="http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style#Punctuation">Punctuation Part</a></li><li><a class="externalLink" href="http://developer.gnome.org/projects/gtp/style-guides/pdf/styleguide-C.pdf">Linguistic Style Guidelines</a>, specifically the "Grammatical Guidelines" chapter.</li></ul></div></div>
+</project></pre></div>
+<p>As you can see above the <tt><distributionManagement></tt> element is indented once (=2 spaces), the <tt><site></tt> element in indented twice (=4 spaces) and the <tt><id></tt> is indented three times (=6 spaces).</p></div></div>
+<div class="section">
+<h3>Naming Documentation Files<a name="Naming_Documentation_Files"></a></h3>
+<p>All file names should replace space by a minus (-), for instance for this given APT document:</p>
+<div class="source">
+<pre> guide-documentation-style.apt</pre></div></div>
+<div class="section">
+<h3>Updating Documentation Files<a name="Updating_Documentation_Files"></a></h3>
+<p>A good practice is to update the date (with the correct date format) when you are updating documentation files.</p></div>
+<div class="section">
+<h3>Write Thinking<a name="Write_Thinking"></a></h3>
+<p>Here are some pointers about English rules when typing material:</p>
+<ul>
+<li><a class="externalLink" href="http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style">Wikipedia:Manual of Style</a>, specifically <a class="externalLink" href="http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style#Punctuation">Punctuation Part</a></li>
+<li><a class="externalLink" href="http://developer.gnome.org/projects/gtp/style-guides/pdf/styleguide-C.pdf">Linguistic Style Guidelines</a>, specifically the "Grammatical Guidelines" chapter.</li></ul></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/guides/development/guide-helping.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/development/guide-helping.html (original)
+++ websites/staging/maven/trunk/content/guides/development/guide-helping.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="Brett Porter
Jason van Zyl" />
<meta name="Date-Creation-yyyymmdd" content="20080703" />
- <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 @@ Jason van Zyl" />
Guide to helping with Maven
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -233,7 +233,47 @@ Jason van Zyl" />
</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>Guide to helping with Maven<a name="Guide_to_helping_with_Maven"></a></h2><p>As with any open source project, there are several ways you can help:</p><ul><li>Join the <a href="../../mail-lists.html">mailing list</a> and answer other user's questions</li><li>Report bugs, feature requests and other issues in the <a href="../../issue-tracking.html">issue tracking</a> application.</li><li><a href="./guide-building-m2.html"> Build Maven</a> for yourself, in order to fix bugs.</li><li><a href="./guide-m2-development.html#Creating_and_submitting_a_patch">Submit patches</a> to reported issues (both those you find, or that others have filed)</li><li><a href="./guide-testing-releases.html"> test releases</a> help test releases that are being voted on (see the dev@maven.apache.org <a href="../../mail-lists.html"> mailing list</a> for release votes</li><li><a href="./guide-testing-development-plugins.html"> test snapshot plugins</a> help t
est the latest development versions of plugins and report issues</li><li>Help with the documentation by pointing out areas that are lacking or unclear, and if you are so inclined, submitting patches to correct it. You can quickly contribute rough thoughts to the <a class="externalLink" href="http://docs.codehaus.org/display/MAVENUSER/"> wiki</a>, or you can volunteer to help collate and organise information that is already there.</li></ul><p>Your participation in the community is much appreciated!</p></div><div class="section"><h2>Why Would I Want to Help?<a name="Why_Would_I_Want_to_Help"></a></h2><p>There are several reasons these are good things.</p><ul><li>By answering other people's questions, you can learn more for yourself</li><li>By submitting your own fixes, they get incorporated faster</li><li>By reporting issues, you ensure that bugs don't get missed, or forgotten</li><li>You are giving back to a community that has given you software for free</li></ul></div><div c
lass="section"><h2>How do I Join the Project?<a name="How_do_I_Join_the_Project"></a></h2><p>Projects at Apache operate under a meritocracy, meaning those that the developers notice participating to a high extent will be invited to join the project as a committer.</p><p>This is as much based on personality and ability to work with other developers and the community as it is with proven technical ability. Being unhelpful to other users, or obviously looking to become a committer for bragging rights and nothing else is frowned upon, as is asking to be made a committer without having contributed sufficiently to be invited.</p></div><div class="section"><h2>Developers Conventions<a name="Developers_Conventions"></a></h2><p>There are a number of conventions used in the project, which contributors and developers alike should follow for consistency's sake.</p><ul><li><a href="../../developers/conventions/code.html">Maven Code Style And Convention</a></li><li><a href="../../develope
rs/conventions/jira.html">Maven JIRA Convention</a></li><li><a href="../../developers/conventions/svn.html">Maven SVN Convention</a></li><li><a href="../../developers/release/releasing.html">Releasing a maven project</a></li></ul></div><div class="section"><h2>Resources for committers<a name="Resources_for_committers"></a></h2><ul><li><a class="externalLink" href="http://www.apache.org/dev/"> Developer Resources</a></li><li><a class="externalLink" href="http://www.apache.org/foundation/"> About the Apache Software Foundation</a></li><li><a class="externalLink" href="http://www.apache.org/dev/committers.html"> Committer FAQ</a></li><li><a class="externalLink" href="http://people.apache.org/~vgritsenko/stats/projects/maven.html"> Web Stats</a></li><li><a class="externalLink" href="http://people.apache.org/~coar/mlists.html#maven.apache.org"> Mailing List Stats</a></li><li><a class="externalLink" href="http://wiki.apache.org/"> Apache Wiki</a></li></ul></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>Guide to helping with Maven<a name="Guide_to_helping_with_Maven"></a></h2>
+<p>As with any open source project, there are several ways you can help:</p>
+<ul>
+<li>Join the <a href="../../mail-lists.html">mailing list</a> and answer other user's questions</li>
+<li>Report bugs, feature requests and other issues in the <a href="../../issue-tracking.html">issue tracking</a> application.</li>
+<li><a href="./guide-building-m2.html"> Build Maven</a> for yourself, in order to fix bugs.</li>
+<li><a href="./guide-m2-development.html#Creating_and_submitting_a_patch">Submit patches</a> to reported issues (both those you find, or that others have filed)</li>
+<li><a href="./guide-testing-releases.html"> test releases</a> help test releases that are being voted on (see the dev@maven.apache.org <a href="../../mail-lists.html"> mailing list</a> for release votes</li>
+<li><a href="./guide-testing-development-plugins.html"> test snapshot plugins</a> help test the latest development versions of plugins and report issues</li>
+<li>Help with the documentation by pointing out areas that are lacking or unclear, and if you are so inclined, submitting patches to correct it. You can quickly contribute rough thoughts to the <a class="externalLink" href="http://docs.codehaus.org/display/MAVENUSER/"> wiki</a>, or you can volunteer to help collate and organise information that is already there.</li></ul>
+<p>Your participation in the community is much appreciated!</p></div>
+<div class="section">
+<h2>Why Would I Want to Help?<a name="Why_Would_I_Want_to_Help"></a></h2>
+<p>There are several reasons these are good things.</p>
+<ul>
+<li>By answering other people's questions, you can learn more for yourself</li>
+<li>By submitting your own fixes, they get incorporated faster</li>
+<li>By reporting issues, you ensure that bugs don't get missed, or forgotten</li>
+<li>You are giving back to a community that has given you software for free</li></ul></div>
+<div class="section">
+<h2>How do I Join the Project?<a name="How_do_I_Join_the_Project"></a></h2>
+<p>Projects at Apache operate under a meritocracy, meaning those that the developers notice participating to a high extent will be invited to join the project as a committer.</p>
+<p>This is as much based on personality and ability to work with other developers and the community as it is with proven technical ability. Being unhelpful to other users, or obviously looking to become a committer for bragging rights and nothing else is frowned upon, as is asking to be made a committer without having contributed sufficiently to be invited.</p></div>
+<div class="section">
+<h2>Developers Conventions<a name="Developers_Conventions"></a></h2>
+<p>There are a number of conventions used in the project, which contributors and developers alike should follow for consistency's sake.</p>
+<ul>
+<li><a href="../../developers/conventions/code.html">Maven Code Style And Convention</a></li>
+<li><a href="../../developers/conventions/jira.html">Maven JIRA Convention</a></li>
+<li><a href="../../developers/conventions/svn.html">Maven SVN Convention</a></li>
+<li><a href="../../developers/release/releasing.html">Releasing a maven project</a></li></ul></div>
+<div class="section">
+<h2>Resources for committers<a name="Resources_for_committers"></a></h2>
+<ul>
+<li><a class="externalLink" href="http://www.apache.org/dev/"> Developer Resources</a></li>
+<li><a class="externalLink" href="http://www.apache.org/foundation/"> About the Apache Software Foundation</a></li>
+<li><a class="externalLink" href="http://www.apache.org/dev/committers.html"> Committer FAQ</a></li>
+<li><a class="externalLink" href="http://people.apache.org/~vgritsenko/stats/projects/maven.html"> Web Stats</a></li>
+<li><a class="externalLink" href="http://people.apache.org/~coar/mlists.html#maven.apache.org"> Mailing List Stats</a></li>
+<li><a class="externalLink" href="http://wiki.apache.org/"> Apache Wiki</a></li></ul></div>
</div>
</div>
<div class="clear">