Apache Maven core
Go to file
Carlos Sanchez Gonzalez 7458db31f5 Remove again the update poms
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@354588 13f79535-47bb-0310-9956-ffa450edef68
2005-12-06 22:08:24 +00:00
benchmark PR: MNG-596 2005-07-21 13:58:42 +00:00
bootstrap Fix bootstrap under windows. 2005-11-17 10:27:31 +00:00
examples/maven-clover-plugin-samples Set a small flush intervalso that the tests execute more rapidly and to ensure it's possible to override it. 2005-10-26 23:19:50 +00:00
integration-tests start moving directories to integration-tests 2005-11-03 05:56:24 +00:00
maven-archiver Backing out changes from MNG-1650, since this was already implemented in the archiver. 2005-12-01 22:20:31 +00:00
maven-artifact PR: MNG-1630 2005-12-06 20:50:41 +00:00
maven-artifact-ant PR: MNG-1466 2005-11-17 16:46:16 +00:00
maven-artifact-manager PR: MNG-1320 2005-11-08 16:25:20 +00:00
maven-artifact-test [maven-release-plugin] prepare for next development iteration 2005-10-14 07:26:39 +00:00
maven-core PR: MNG-1352 2005-12-06 16:34:09 +00:00
maven-core-it Adding install step. 2005-12-06 19:19:35 +00:00
maven-core-it-verifier Use mvn command instead of deprecated m2 2005-12-01 07:48:50 +00:00
maven-embedder o use the correct method 2005-11-05 18:08:38 +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 PR: MNG-1721 2005-12-01 17:04:09 +00:00
maven-meeper Remove again the update poms 2005-12-06 22:08:24 +00:00
maven-model [maven-release-plugin] prepare for next development iteration 2005-10-14 07:26:39 +00:00
maven-model-converter rely on managed versions 2005-11-30 20:03:30 +00:00
maven-monitor [maven-release-plugin] prepare for next development iteration 2005-10-14 07:26:39 +00:00
maven-plugin-api [maven-release-plugin] prepare for next development iteration 2005-10-14 07:26:39 +00:00
maven-plugin-descriptor clean some imports and unused code 2005-10-23 23:50:38 +00:00
maven-plugin-parameter-documenter clean some imports and unused code 2005-10-23 23:50:38 +00:00
maven-plugin-registry [maven-release-plugin] prepare for next development iteration 2005-10-14 07:26:39 +00:00
maven-plugin-tools PR: MNG-1525 2005-12-06 16:28:07 +00:00
maven-profile PR: MNG-1525 2005-12-06 16:28:07 +00:00
maven-project PR: MNG-1630 2005-12-06 20:50:41 +00:00
maven-reporting add names 2005-11-01 04:19:00 +00:00
maven-repository-metadata [maven-release-plugin] prepare for next development iteration 2005-10-14 07:26:39 +00:00
maven-repository-tools PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-script Ant support is working. I want to revisit the testing before I let it go, though. 2005-10-19 04:14:13 +00:00
maven-settings PR: MNG-1525 2005-12-06 16:28:07 +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 always call $JAVA_HOME/bin/java 2005-11-21 22:42:41 +00:00
ci.sh update plugins too as long as we are still building them 2005-12-05 01:43:27 +00:00
pom.xml switch Apache snapshots to Apache repo 2005-11-29 11:25:04 +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>