Apache Maven core
Go to file
Brett Leslie Porter 51b55e42ff merge r377583 from branch 2.0.x
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@377591 13f79535-47bb-0310-9956-ffa450edef68
2006-02-14 02:55:13 +00:00
bootstrap flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
integration-tests [MNG-1927] This adds the test mojos required to fix ${pom.build.*} expansion to full paths, the problem was the 2006-01-11 19:36:37 +00:00
maven-archiver flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-artifact merge r377583 from branch 2.0.x 2006-02-14 02:55:13 +00:00
maven-artifact-ant merge from branch maven-2.0.x, up to rev 365776 2006-01-04 01:14:17 +00:00
maven-artifact-manager [MNG-1908] correct error introduced in last rev with locally installed snapshots 2006-02-07 05:51:14 +00:00
maven-artifact-test Fix problem where settings.xml doesn't contain localRepo 2006-02-11 03:28:20 +00:00
maven-core remove testing descriptor 2006-02-09 00:14:08 +00:00
maven-core-it o updating README.txt and adding another IT for the duplicate IDs 2006-02-07 03:36:52 +00:00
maven-core-it-verifier Use mvn command instead of deprecated m2 2005-12-01 07:48:50 +00:00
maven-embedder o creating a mode for aligning the the embedder with a user installation 2006-01-19 07:19:04 +00:00
maven-embedder-it git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@291718 13f79535-47bb-0310-9956-ffa450edef68 2005-09-26 19:23:47 +00:00
maven-error-diagnostics flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-meeper Exclude all .* files 2006-02-13 19:03:23 +00:00
maven-model upgrade modello 2006-02-07 01:53:48 +00:00
maven-model-converter Make site deploy to maven.apache.org/ref/version with jxr and javadocs reports 2006-02-01 02:39:10 +00:00
maven-monitor flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-plugin-api flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-plugin-descriptor flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-plugin-parameter-documenter flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-plugin-registry flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-plugin-tools flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-profile flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-project [MNG-1980] Removing the duplicate ID, the reactor will catch duplicate IDs in a single build so it doesn't not need 2006-01-21 16:36:06 +00:00
maven-reporting add deprecation warnings for 2.1 2006-02-07 04:58:06 +00:00
maven-repository-metadata flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-repository-tools PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-script flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
maven-settings flip trunk to 2.1-SNAPSHOT 2005-12-12 18:22:06 +00:00
README.txt switch bootstrap 2005-11-16 13:31:15 +00:00
bootstrap.bat Fix bootstrap under windows. 2005-11-17 10:27:31 +00:00
bootstrap.sh o we're not going to build the plugins so make sure that someone who has checked out the "maven" 2005-12-23 05:23:17 +00:00
ci.sh minor adjustments to ci 2005-12-21 13:33:06 +00:00
pom.xml Use my new address 2006-02-08 15:21:41 +00:00

README.txt

-------------------------------------------------------------------------------
Bootstrapping Maven
-------------------------------------------------------------------------------

Set the environment variable M2_HOME pointing to the dir where you want Maven2 installed.

NOTE: presently, the directory {M2_HOME}/bin must be in your path:
set PATH=%PATH%;%M2_HOME%\bin
or
export PATH=$PATH:$M2_HOME/bin

You can set the parameters passed to the Java VM when running Maven2 bootstrap,
setting the environment variable MAVEN_OPTS, e.g.
e.g. to run in offline mode, set MAVEN_OPTS=-o

Then run bootstrap.bat (in Windows) or bootstrap.sh (in Unix)

NOTE: You must run these instructions from this directory!

If you are behind a firewall, you will need to let the bootstrap process know.
To do this, create a file at ~/.m2/settings.xml and paste in the XML below,
substituting your settings for those provided. You can safely skip the
username, password and nonProxyHost elements if they are not relevant to you.

<settings>
  <proxies>
    <proxy>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy.somewhere.com</host>
      <port>8080</port>
      <username>proxyuser</username>
      <password>somepassword</password>
      <nonProxyHosts>www.google.com|*.somewhere.com</nonProxyHosts>
    </proxy>
  </proxies>
</settings>