mirror of https://github.com/apache/maven.git
0cc696a407
o Implemented plan from my comments on MNG-576 for looking up lifecycle mappings within plugins. o Fixed subtle bug in DefaultWagonManager for verifying checksums, where the destination file was being used to verify the checksum rather than the recently download temp destination. o Fixed the DefaultRepositoryMetadataManager.resolve(..) method to allow the locally-installed metadata to be used if it is newer than the one resolved from the repository. o Moved the lifecycle mappings for the EJB and WAR plugins out to META-INF/plexus/components.xml in the respective plugin's src/main/resources directory. it0016 and it0017 still pass. o Changed the distributionManagement repository for maven-plugins/pom.xml to have id of 'central-plugins' and then added a normal artifact repository definition for central-plugins to that pom, to allow locally-installed repository metadata for the plugins to be put in the right place (and these builds should have access to the central plugin repo anyway). o Changed the DefaultPluginMappingBuilder to only warn when plugins.xml for a particular plugin group is missing. git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@216273 13f79535-47bb-0310-9956-ffa450edef68 |
||
---|---|---|
benchmark | ||
examples/maven-hello-plugin | ||
maven-1.x-integration | ||
maven-archetype | ||
maven-archiver | ||
maven-artifact | ||
maven-artifact-ant | ||
maven-artifact-manager | ||
maven-artifact-test | ||
maven-core | ||
maven-core-it | ||
maven-core-it-plugin | ||
maven-core-it-support | ||
maven-core-it-verifier | ||
maven-mboot2 | ||
maven-meeper | ||
maven-model | ||
maven-monitor | ||
maven-plugin-api | ||
maven-plugin-descriptor | ||
maven-plugin-mapping | ||
maven-plugin-registry | ||
maven-plugin-tools | ||
maven-plugins | ||
maven-profile | ||
maven-project | ||
maven-reporting | ||
maven-reports | ||
maven-repository-tools | ||
maven-script | ||
maven-settings | ||
maven-site | ||
sandbox | ||
README.txt | ||
ci.sh | ||
m2-bootstrap-all.bat | ||
m2-bootstrap-all.sh | ||
plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt | ||
pom.xml | ||
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>