mirror of https://github.com/apache/maven.git
701ef520a3
o Changed MavenMetadataSource to a component, to avoid having to lookup artifactFactory and projectBuilder in order to construct it. o Added add(..) method to ScmBean in the release plugin to allow addition of release-pom.xml o Changed the PrepareReleaseMojo to resolve ONLY version and parent-version for the normal pom.xml, and fully resolve all artifacts used in the release-pom.xml, including version, parent-version, dependency closure (given by project.getArtifacts()), plugins, and reports. It will then add the release-pom.xml, and (attempt to) delete it before performing the final commit for next development version. o Added some mapping methods to ArtifactUtils, to key by artifact.getId, and to create an Artifact.getId()-compatible string from parameters. o Added TestProjectBuilder to remove the requirement in ProjectClasspathTest to modify the fields of the project builder directly. o Cleaned up the AbstractReleaseMojo and PrepareReleaseMojo to avoid container lookups...they're now mojo parameters with the 'component.' prefix. NOTE: Next step is to figure out how to use maven-scm to remove an SCM resource, to enable the prepare mojo to take the release-pom.xml back out of HEAD after the tag is complete. git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@224413 13f79535-47bb-0310-9956-ffa450edef68 |
||
---|---|---|
benchmark | ||
examples | ||
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-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>