You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ah...@apache.org on 2006/04/19 00:17:31 UTC
svn commit: r395073 -
/maven/maven-1/core/trunk/xdocs/developers/building-from-source.xml
Author: aheritier
Date: Tue Apr 18 15:17:28 2006
New Revision: 395073
URL: http://svn.apache.org/viewcvs?rev=395073&view=rev
Log:
Update doc about the new directories layout used by the bootstrap.
Modified:
maven/maven-1/core/trunk/xdocs/developers/building-from-source.xml
Modified: maven/maven-1/core/trunk/xdocs/developers/building-from-source.xml
URL: http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/developers/building-from-source.xml?rev=395073&r1=395072&r2=395073&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/developers/building-from-source.xml (original)
+++ maven/maven-1/core/trunk/xdocs/developers/building-from-source.xml Tue Apr 18 15:17:28 2006
@@ -71,8 +71,7 @@
Subversion repositories. For example, using the command line:
</p>
<source><![CDATA[
-svn co http://svn.apache.org/repos/asf/maven/maven-1/core/trunk maven-1/core/trunk
-svn co http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk maven-1/plugins/trunk]]></source>
+svn co http://svn.apache.org/repos/asf/maven/maven-1/trunks maven-1]]></source>
<p>
After setting the value of <code>MAVEN_HOME</code> and
pulling down the sources you are now ready to
@@ -80,7 +79,7 @@
process. As mentioned earlier, the bootstrapping process is
defined in <code>build-bootstrap.xml</code>, and can be
initiated by typing the following from the
- <code>maven-1/core/trunk</code> directory:
+ <code>maven-1/core</code> directory:
</p>
<source><![CDATA[ant -f build-bootstrap.xml]]></source>
<p>
@@ -100,14 +99,14 @@
<section name="Building Maven with Maven">
<p>
This section explains how to build Maven with Maven already installed.
- This assumes that you have the <code>maven-1/core/trunk</code> tree checked out.
- Unlike the bootstrap, the <code>maven-1/plugins/trunk</code> tree is not required
+ This assumes that you have the <code>maven-1/core</code> tree checked out.
+ Unlike the bootstrap, the <code>maven-1/plugins</code> tree is not required
as the following goals will download (if necessary) the latest plugin releases
and use those instead of building them from sources. If you wish to do this, please
read <a href="#Building_Plugins_From_Sources">Building Plugins From Sources</a>.
</p>
<p>
- Start by running <code>maven -u</code> in the <code>maven-1/core/trunk</code> directory.
+ Start by running <code>maven -u</code> in the <code>maven-1/core</code> directory.
This will give you a quick overview of the defined goals.
</p>
<subsection name="Building a Complete Maven Installation">
@@ -172,8 +171,8 @@
</subsection>
<subsection name="Building Plugins From Sources">
<p>
- To build the plugins from sources, you need to have <code>maven-1/plugins/trunk</code>
- checked out from Subversion at the same level as the <code>maven-1/core/trunk</code> tree (not underneath it).
+ To build the plugins from sources, you need to have <code>maven-1/plugins</code>
+ checked out from Subversion at the same level as the <code>maven-1/core</code> tree (not underneath it).
</p>
<p>
These goals have some common logic: they invoke the reactor on the plugins
@@ -188,28 +187,44 @@
</p>
<table>
<tr>
- <td>maven:plugins-install</td>
+ <td>plugins:install-all</td>
<td>
Clean, build and install each Maven plugin into the running Maven installation (though they will not
be utilised until next execution). This is the most commonly used goal.
</td>
</tr>
<tr>
- <td>maven:plugins-test</td>
+ <td>plugins:test-all</td>
<td>Test each Maven plugin. This runs any integration tests available for individual plugins.</td>
</tr>
<tr>
- <td>maven:plugins-clean</td>
+ <td>plugins:repository-deploy-all</td>
<td>
- Cleans all plugin projects.
+ Deploy all plugins in a remote repository.
</td>
</tr>
<tr>
- <td>maven:plugins-build</td>
+ <td>plugins:site</td>
<td>
- Build each Maven plugin into an installable jar. The plugins are
- not actually installed, so this is useful simply to see if they all
- build.
+ Create the web site root for all plugins.
+ </td>
+ </tr>
+ <tr>
+ <td>plugins:build-all-sites</td>
+ <td>
+ Create the web site for all plugins and for the root site.
+ </td>
+ </tr>
+ <tr>
+ <td>plugins:deploy-all-sites</td>
+ <td>
+ Deploy the web site for all plugins and for the root site.
+ </td>
+ </tr>
+ <tr>
+ <td>plugins:publish-all-sites</td>
+ <td>
+ Publish the web site for all plugins and for the root site.
</td>
</tr>
</table>