mirror of https://github.com/apache/maven.git
cda19f2e5c
o During addPlugin() only the plugin's artifact is resolved/added...just enough to get the plugin container to discover the pluginDescriptor. o During getConfiguredMojo(), the rest of the plugin's artifacts will be transitively resolved and added to the plugin container (if this hasn't already been done). The deciding factor for attempting to complete the plugin container's artifact list is whether the only artifact in the pluginDescriptor's artifact list is the plugin artifact itself. If that makes sense. It's a bit of black magic, but I think it'll work unless/until we find something more elegant. I'm abusing the container a little bit here, so it might be sensitive to plexus changes in future. git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@191582 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-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-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!