From 1c0f134fa562516f6ad935451c2deee278a44490 Mon Sep 17 00:00:00 2001 From: Brett Leslie Porter Date: Sun, 12 Jun 2005 04:51:48 +0000 Subject: [PATCH] add building doc git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@190215 13f79535-47bb-0310-9956-ffa450edef68 --- maven-site/src/site/apt/building.apt | 74 ++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) create mode 100644 maven-site/src/site/apt/building.apt diff --git a/maven-site/src/site/apt/building.apt b/maven-site/src/site/apt/building.apt new file mode 100644 index 0000000000..496fc2c653 --- /dev/null +++ b/maven-site/src/site/apt/building.apt @@ -0,0 +1,74 @@ + ------ + Building Maven 2.0 + ------ + Brett Porter + ------ + 12 June 2005 + ------ + +Building Maven 2.0 + +* Why would I want to build Maven 2.0? + + Building Maven 2.0 yourself is for one of two reasons: + + * to try out a bleeding edge feature or bugfix + + * to fix a problem you are having and submit a patch to the developers team. + + 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. + +* Checking out the sources + + All of the source code for Maven 2.0 and its related libraries are in Subversion. You can + {{{http://svn.apache.org/viewcvs.cgi/maven/} browse the repository}}, or checkout specific modules directly. + + To build Maven 2.0, you need the <<>> module. To check that out, run the command: + +------------------- +svn co http://svn.apache.org/repos/asf/maven/components/trunk maven-components +------------------- + + The <<>> directory will contain the source code. Note that this contains all of the plugins and + the Ant tasks. + + Other modules you might be interested in related to Maven development are: + + * <<>> - Maven Wagon, used by the artifact code and others for providing the transport layer to + get and put artifacts in a repository. + + * <<>> - Maven SCM, a generic API to communicate with various different SCM providers, used by + Continuum and the release and SCM plugins. + + * {{{http://svn.plexus.codehaus.org/plexus/} Plexus}} - the IoC container used by Maven. + +* Building Maven + + Once you have checked out the code, change into the <<>> directory that was created. + You may want to setup a different environment to install Maven to other than your normal installation of a + release, so set the <<>> environment variable accordingly, e.g.: + +---- +export M2_HOME=/usr/local/maven-2.0-SNAPSHOT +PATH=$M2_HOME/bin:$PATH + or +set M2_HOME=c:\maven-2.0-SNAPSHOT +set PATH=%M2_HOME%\bin;$PATH +---- + + From this, run the <<>> command for your system: + +---- +sh m2-bootstrap-all.sh + or +m2-bootstrap-all.bat +---- + + First, the code will be built, then using the new installation the plugins will be rebuilt and installed in the + local repository. Finally, a set of integration tests will run. + + If you have any problems or get any failures during the run, please report them to the + {{{/mail-lists.html} Maven Developers List}}. + +