Apache Maven core
Go to file
Brett Leslie Porter 39b9565855 PR: MNG-484
Submitted by: Binyan
Reviewed by:  Brett Porter
add file:// deployment mechanism to site:deploy

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@292366 13f79535-47bb-0310-9956-ffa450edef68
2005-09-29 01:18:09 +00:00
benchmark PR: MNG-596 2005-07-21 13:58:42 +00:00
examples Added again <defaultExcludes>. Apparently is was a problem with my version of m2. Sorry for the noise. 2005-09-23 12:14:09 +00:00
maven-1.x-integration match interface and impl 2005-09-16 07:07:51 +00:00
maven-archetype o adding a description to the archetype mojo 2005-09-24 13:31:22 +00:00
maven-archiver [maven-release-plugin] prepare for next development iteration 2005-09-26 15:30:36 +00:00
maven-artifact PR: MNG-916 2005-09-28 13:07:53 +00:00
maven-artifact-ant [maven-release-plugin] prepare for next development iteration 2005-09-26 15:30:36 +00:00
maven-artifact-manager o adding the name to the deploy plugin metadata so that i can pull it down 2005-09-28 22:56:41 +00:00
maven-artifact-test [maven-release-plugin] prepare for next development iteration 2005-09-26 15:30:36 +00:00
maven-core add mojo project as a default group 2005-09-29 00:29:03 +00:00
maven-core-it Adding goals specification to fix this test. 2005-09-28 20:16:53 +00:00
maven-core-it-plugin use inherited version 2005-09-28 23:27:30 +00:00
maven-core-it-support fix snapshot repo 2005-09-26 13:31:30 +00:00
maven-core-it-verifier Adding file-pattern matching for expected results, along with ability to suppress the default maven.repo.local specification from verifier.properties...also, adding a test case for MNG-1021, to ensure the source artifact has the same build number as the main jar...I cannot reproduce the problem using this test... 2005-09-28 20:14:35 +00:00
maven-embedder o updating the metadata for the core and bumping the version in the scripts 2005-09-28 23:08:41 +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-mboot2 remove legacy metadata handling 2005-09-28 10:12:38 +00:00
maven-meeper Use new repodir 2005-08-31 22:54:08 +00:00
maven-model [maven-release-plugin] prepare for next development iteration 2005-09-26 15:30:36 +00:00
maven-monitor [maven-release-plugin] prepare for next development iteration 2005-09-26 15:30:36 +00:00
maven-plugin-api Storing plugin contexts by plugin and project in the release manager, and furnishing access to them via the session. This will restrict shared information scopes to the plugin AND the project, in a reactored situation. 2005-09-28 03:38:00 +00:00
maven-plugin-descriptor PR: MNG-817 2005-09-28 05:09:14 +00:00
maven-plugin-registry Fixed default updateInterval (add missing 'interval:' prefix) 2005-09-27 12:03:56 +00:00
maven-plugin-tools PR: MNG-817 2005-09-28 05:09:14 +00:00
maven-plugins PR: MNG-484 2005-09-29 01:18:09 +00:00
maven-profile [maven-release-plugin] prepare for next development iteration 2005-09-26 15:30:36 +00:00
maven-project Resolving: MNG-985...simply fixed merging of plugins from PluginManagement to happen on a plugin-by-plugin basis using individual merge logic from ModelUtils, rather than the wholesale merge logic for plugin lists. 2005-09-28 18:57:22 +00:00
maven-reporting PR: MNG-706 2005-09-26 16:41:53 +00:00
maven-repository-metadata o adding the name to the deploy plugin metadata so that i can pull it down 2005-09-28 22:56:41 +00:00
maven-repository-tools PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-script PR: MNG-817 2005-09-28 05:09:14 +00:00
maven-settings [maven-release-plugin] prepare for next development iteration 2005-09-26 15:30:36 +00:00
maven-site o adding the name to the deploy plugin metadata so that i can pull it down 2005-09-28 22:56:41 +00:00
sandbox o sketch of how the code in here might be replaced with the embedder 2005-09-26 21:30:03 +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 fix in case of a non-existant local repo 2005-07-26 15:11:21 +00:00
m2-bootstrap-all.sh fix in case of a non-existant local repo 2005-07-26 15:11:21 +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 [maven-release-plugin] prepare for next development iteration 2005-09-26 15:30:36 +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>