Apache Maven core
Go to file
John Dennis Casey 5f190db3d6 Adding test case for MNG-1424.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@344260 13f79535-47bb-0310-9956-ffa450edef68
2005-11-14 23:04:56 +00:00
benchmark PR: MNG-596 2005-07-21 13:58:42 +00:00
bootstrap create a bootstrap installation 2005-11-14 13:38:14 +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 [maven-release-plugin] prepare for next development iteration 2005-10-14 07:26:39 +00:00
maven-artifact Fixing CI process. Children of system scoped deps were not being excluded properly...I had marked it to exclude the system scoped dep as well. 2005-11-10 16:04:56 +00:00
maven-artifact-ant add names 2005-11-01 04:19:00 +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-1424 2005-11-14 22:55:49 +00:00
maven-core-it Adding test case for MNG-1424. 2005-11-14 23:04:56 +00:00
maven-core-it-verifier delete metadata files for all versions to ensure intergration test works as expected 2005-10-19 04:54:57 +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 merge from tag maven-2.0, rev 326248 2005-10-18 21:16:22 +00:00
maven-mboot2 fix warnings 2005-11-11 07:47:04 +00:00
maven-meeper Take everything under org.mortbay 2005-11-14 21:13:59 +00:00
maven-model [maven-release-plugin] prepare for next development iteration 2005-10-14 07:26:39 +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-897 2005-11-01 01:25:19 +00:00
maven-plugins Bumping Plugin-Parent version to 2.0.1-SNAPSHOT to reference API changes to MavenProjectHelper, and changing maven-assembly-plugin's pom to reference that new parent POM. 2005-11-14 22:52:06 +00:00
maven-profile [maven-release-plugin] prepare for next development iteration 2005-10-14 07:26:39 +00:00
maven-project Forgot to open up these two methods via the interface... 2005-11-08 19:48:57 +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 o adding a note about the default location of the settings file 2005-10-27 19:41:37 +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 only mail about skipped run on checkout attempt to allow overlap 2005-07-28 01:17:38 +00:00
m2-bootstrap-all.bat use mvn instead of m2 2005-10-31 16:37:09 +00:00
m2-bootstrap-all.sh use mvn instead of m2 2005-10-31 16:37:09 +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 don't build by default 2005-11-11 15:05:37 +00:00
upgrading-dependencies.apt

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>