mirror of https://github.com/apache/maven.git
63aab278c2
o Added component descriptor for the MavenPluginMappingBuilder o Added a new ComponentDiscoveryListener implementation to factor the DefaultPluginManager out of the plexus.xml for maven-core...the DefaultPluginManager now delegates to this component for plugin registration/lookup/etc. and has proper component requirements. o Moved the DefaultPluginManager component declaration into components.xml, and added a component definition for MavenPluginCollector to plexus.xml in maven-core Next step is to get rid of the old pluginKey junk, and start using o.a.m.Plugin instances to hold g🅰️v info for all plugins in the system...this will make the interface cleaner and remove the need to concat/parse the plugin identity. Then, I'll add the mapped-plugin lookup functionality to the lifecycle executor. git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@209563 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>