You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by bu...@apache.org on 2015/01/04 18:34:05 UTC
svn commit: r935028 - in /websites/staging/maven/trunk/content: ./
guides/development/guide-building-m2.html maven-site-1.0-site.jar
Author: buildbot
Date: Sun Jan 4 17:34:04 2015
New Revision: 935028
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 Sun Jan 4 17:34:04 2015
@@ -1 +1 @@
-1649361
+1649371
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 Sun Jan 4 17:34:04 2015
@@ -14,7 +14,7 @@
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Brett Porter
Jason van Zyl" />
- <meta name="Date-Creation-yyyymmdd" content="20121220" />
+ <meta name="Date-Creation-yyyymmdd" content="20150104" />
<meta name="Date-Revision-yyyymmdd" content="20150104" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -251,121 +251,51 @@ Jason van Zyl" />
<h3><a name="Why_would_I_want_to_build_Maven"></a>Why would I want to build Maven?</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 try out a bleeding edge feature or bugfix (issues can be found in <a href="/issue-tracking.html"> 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><a name="Checking_out_the_sources"></a>Checking out the sources</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>HEAD</tt> of the <tt>maven</tt> module. To check that out, run the command:</p>
-<div class="source">
-<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 from a cloned repository, run the command:</p>
-<div class="source">
-<pre>git checkout maven-2.2.x</pre></div>
-<div class="section">
-<h4><a name="Other_Modules"></a>Other Modules</h4>
-<p>Other modules you might be interested in related to Maven development are:</p>
-<ul>
-<li><tt>maven-integration-testing</tt> - <tt>git clone https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git</tt></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. <tt>git clone https://git-wip-us.apache.org/repos/asf/maven-scm.git</tt></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. <tt>git clone https://git-wip-us.apache.org/repos/asf/maven-surefire.git</tt></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>
+<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></div>
<div class="section">
<h3><a name="Building_Maven"></a>Building Maven</h3>
<div class="section">
+<h4><a name="Building_a_Maven_Plugin_or_Component"></a>Building a Maven Plugin or Component</h4>
+<p>Building a Maven plugin or component is like any Maven build:</p>
+<div class="source">
+<pre>mvn install</pre></div>
+<p>Before submitting a patch, it is advised to run the integration tests, which are available in a profile:</p>
+<div class="source">
+<pre>mvn -Prun-its install</pre></div></div>
+<div class="section">
<h4><a name="Building_Maven_With_Maven_Installed"></a>Building Maven With Maven Installed</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>
+<p>To do this, run from the source directory:</p>
+<div class="source">
<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><a name="Running_the_full_integration_tests"></a>Running the full integration tests</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>
+<p>The assemblies will be created in <tt>maven-distribution</tt>, and can be unzipped to the location where you'd like Maven installed.</p></div>
<div class="section">
<h4><a name="Building_Maven_Without_Maven_Installed"></a>Building Maven Without Maven Installed</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
+<p>Once you have checked out the code, change into the directory that was created.</p>
+<p>Set the <tt>M2_HOME</tt> 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-3.2.x-SNAPSHOT</tt>.</p>
+<div class="source">
+<pre>export M2_HOME=/usr/local/maven-3.2.x-SNAPSHOT
PATH=$M2_HOME/bin:$PATH</pre></div>
<p>or</p>
-<div>
-<pre>set M2_HOME=c:\maven-2.2-SNAPSHOT
+<div class="source">
+<pre>set M2_HOME=c:\maven-3.2.x-SNAPSHOT
set PATH=%M2_HOME%\bin;%PATH%</pre></div>
<p>From this, run the <tt>ant</tt> command:</p>
-<div>
+<div class="source">
<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>
+<p>This will download dependencies, build Maven, and install it into the directory you specified as <tt>M2_HOME</tt> above.</p></div>
+<div class="section">
+<h4><a name="Running_the_full_Maven_core_integration_tests"></a>Running the full Maven core integration tests</h4>
+<p>Before checking in a change or submitting a patch to Maven core, it is required to run the integration tests. These live in their own git repository. Using your local build of Maven, run:</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
- Maven again in this directory and generate an installation assembly. Then we
- extract the assembly and re-run the Maven build one more time, this time
- with the full generated Maven.
-
- To run this script, you must set the M2_HOME environment variable or the
- maven.home property to the location that should contain Maven. This
- directory *must* be named after the maven version you want to install, e.g.
- /usr/local/maven-2.1-SNAPSHOT.
-
- You can set the maven.repo.local property to specify a custom location for
- your local repository for the bootstrap process.
-
-Main targets:
-
- classpath-pre constructs a classpath reference containing our dependencies,
- and verifies that all files are present
-
- clean-bootstrap cleans up generated bootstrap classes
-
- compile-boot compiles the bootstrap sources
-
- extract-assembly extracts the maven assembly into maven.home
-
- generate-sources generates Java sources from Modello mdo model files
-
- maven-assembly generates the Maven installation assembly using the bootstrap
- Maven
-
- maven-compile compiles Maven using the bootstrap Maven, skipping automated
- tests
-
- pull copies all required dependencies from the Maven remote
- repository into your local repository. Set the 'skip.pull'
- property to skip this step, but only if you're sure you
- already have all of the dependencies downloaded to
- your local repository
-
- run-full-maven runs the full extracted Maven, now with tests
-
-Default target: all</pre></div></div></div></div>
+<pre>mvn install -Prun-its</pre></div>
+<p>Consult <a href="/core-its/core-it-suite/">Core IT Suite documentation</a> for more options.</p></div></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.