Apache Maven core
Go to file
Brett Leslie Porter 17991ceea7 cleanup
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@225317 13f79535-47bb-0310-9956-ffa450edef68
2005-07-26 14:41:35 +00:00
benchmark PR: MNG-596 2005-07-21 13:58:42 +00:00
examples PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-1.x-integration PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-archetype PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-archiver PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-artifact cleanup 2005-07-26 14:41:35 +00:00
maven-artifact-ant PR: MNG-456 2005-07-25 09:51:12 +00:00
maven-artifact-manager o Fixing resolution of LATEST in plugin-versions, when <useLatest/> is enabled in plugin-registry.xml, or when --check-plugin-latest is specified on the command line. 2005-07-26 05:54:24 +00:00
maven-artifact-test PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-core move main J2EE packaging definitions back to being built in 2005-07-26 14:00:23 +00:00
maven-core-it snapshots have moved 2005-07-26 14:24:38 +00:00
maven-core-it-plugin PR: MNG-598 2005-07-26 09:04:32 +00:00
maven-core-it-support PR: MNG-598 2005-07-26 09:04:32 +00:00
maven-core-it-verifier use a file that has to be there :) 2005-07-26 05:57:26 +00:00
maven-mboot2 this is supposed to be preloaded to the remote repository for integration testing purposes 2005-07-22 00:08:46 +00:00
maven-meeper PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-model PR: MNG-598 2005-07-26 09:04:32 +00:00
maven-monitor PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-plugin-api PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-plugin-descriptor Working on MNG-607 2005-07-22 22:07:28 +00:00
maven-plugin-mapping PR: MNG-598 2005-07-26 09:04:32 +00:00
maven-plugin-registry PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-plugin-tools PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-plugins no need for the manager - it is stored in the artifact 2005-07-26 14:22:13 +00:00
maven-profile PR: MNG-456 2005-07-25 09:51:12 +00:00
maven-project o Fixing resolution of LATEST in plugin-versions, when <useLatest/> is enabled in plugin-registry.xml, or when --check-plugin-latest is specified on the command line. 2005-07-26 05:54:24 +00:00
maven-reporting remove deprecation that was intended to happen, but the other changes got backed out 2005-07-26 12:14:27 +00:00
maven-repository-tools PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-script PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-settings o Fixing resolution of LATEST in plugin-versions, when <useLatest/> is enabled in plugin-registry.xml, or when --check-plugin-latest is specified on the command line. 2005-07-26 05:54:24 +00:00
maven-site PR: MNG-596 2005-07-21 13:58:42 +00:00
sandbox PR: MNG-596 2005-07-21 13:58:42 +00:00
README.txt o applying patch provided with: http://jira.codehaus.org/browse/MNG-499 2005-07-06 00:24:22 +00:00
ci.sh on Solaris, need to source the profile stuff 2005-07-21 00:52:22 +00:00
m2-bootstrap-all.bat move reports into maven-plugins 2005-07-21 02:20:27 +00:00
m2-bootstrap-all.sh doesn't accept -D args 2005-07-26 06:11:52 +00:00
plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt adding my notes for implementing plugin inheritance and build profiles. delete if not needed. 2005-05-27 03:29:54 +00:00
pom.xml PR: MNG-456 2005-07-25 09:51:12 +00:00
upgrading-dependencies.apt some notes on changing dependencies 2004-10-23 13:28:06 +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 m2-bootstrap-all.bat (in Windows) or m2-bootstrap-all.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>