maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r845345 - in /websites/staging/maven/trunk/content: ./ guides/development/guide-building-m2.html maven-site-1.0-site.jar
Date Mon, 07 Jan 2013 15:46:54 GMT
Author: buildbot
Date: Mon Jan  7 15:46:53 2013
New Revision: 845345

Log:
Staging update by buildbot for maven

Modified:
    websites/staging/maven/trunk/content/   (props changed)
    websites/staging/maven/trunk/content/guides/development/guide-building-m2.html
    websites/staging/maven/trunk/content/maven-site-1.0-site.jar

Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan  7 15:46:53 2013
@@ -1 +1 @@
-1429805
+1429854

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 Mon Jan
 7 15:46:53 2013
@@ -230,7 +230,7 @@ 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 <a class="externalLink" href="http://subversion.apache.org/">
Subversion</a>. You can <a class
 ="externalLink" href="http://svn.apache.org/viewvc/maven/"> browse the repository</a>,
or checkout specific modules directly.</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">/
 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="Buil
 ding_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-integratio
 n-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
+        <!-- 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">/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 t
 he 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
 

Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.



Mime
View raw message