Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Apache Maven core
1,179 Commits 84 Branches 94 Tags 109 MiB
Java 99.7%
Shell 0.1%
Batchfile 0.1%
Go to file
John Dennis Casey dc92832ad2 o Fixed bash scripts (cygwin option was being tested incorrectly, and resulting in no such file: cygpath) 
o Changed POM handling to use ArtifactMetadata API rather than direct Artifact construction for POMs
o Streamlined ArtifactDigestor to avoid use of byte arrays for transfer between methods (resulted in a bit of cut-and-paste code, but should run better)
o Pegged OutOfMemoryError to the ArtifactDigestVerifier/ArtifactDigestor combo (motivated the previous change)
o Cleaned up artifact source-file checking before creating any of the target directory structures
o Maybe works, maybe not...will resume testing tomorrow or the next day


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163743 13f79535-47bb-0310-9956-ffa450edef68
 		2005-04-02 02:17:19 +00:00
benchmark change the maven group ID 2005-03-23 06:52:55 +00:00
maven-1.x-integration change the maven group ID 2005-03-23 06:52:55 +00:00
maven-archetype update poms for releases 2005-04-01 16:03:43 +00:00
maven-archiver update poms for releases 2005-04-01 16:03:43 +00:00
maven-artifact update poms for releases 2005-04-01 16:03:43 +00:00
maven-core treat empty expressions as non-existant 2005-04-01 16:14:30 +00:00
maven-core-it update poms for releases 2005-04-01 16:03:43 +00:00
maven-core-it-plugin change the maven group ID 2005-03-23 06:52:55 +00:00
maven-core-it-support change the maven group ID 2005-03-23 06:52:55 +00:00
maven-core-it-verifier change the maven group ID 2005-03-23 06:52:55 +00:00
maven-mboot2 update poms for releases 2005-04-01 16:03:43 +00:00
maven-meeper commit outstanding changes 2005-03-29 00:10:35 +00:00
maven-model implement snapshot policies: default is to only check once a day (after crossing midnight), or if --update-snapshots (-U) is specified on the command line 2005-03-30 03:30:08 +00:00
maven-monitor change the maven group ID 2005-03-23 06:52:55 +00:00
maven-plugin fix stale source scanner 2005-03-30 05:52:07 +00:00
maven-plugin-tools update poms for releases 2005-04-01 16:03:43 +00:00
maven-plugins update poms for releases 2005-04-01 16:03:43 +00:00
maven-reporting-api change the maven group ID 2005-03-23 06:52:55 +00:00
maven-repository-tools change the maven group ID 2005-03-23 06:52:55 +00:00
maven-script o Adding <modules>. 2005-03-29 21:36:47 +00:00
maven-settings change the maven group ID 2005-03-23 06:52:55 +00:00
sandbox o Fixed bash scripts (cygwin option was being tested incorrectly, and resulting in no such file: cygpath) 2005-04-02 02:17:19 +00:00
.cvsignore o Added plugin version management/enforcement through the POM's build section. 2005-03-10 21:36:58 +00:00
README.txt Added debug option to compiler configuration. 2005-01-09 22:38:43 +00:00
ci.sh wrong date format 2004-09-20 05:13:19 +00:00
m2-bootstrap-all.bat update poms for releases 2005-04-01 16:03:43 +00:00
m2-bootstrap-all.sh update poms for releases 2005-04-01 16:03:43 +00:00
pom.xml update poms for releases 2005-04-01 16:03:43 +00:00
upgrading-dependencies.apt some notes on changing dependencies 2004-10-23 13:28:06 +00:00

README.txt 

-------------------------------------------------------------------------------
Bootstrapping Maven
-------------------------------------------------------------------------------

To bootstrap Maven you must have a ~/.m2/maven.properties file with the following
entry:

maven.repo.local = /path/to/your/local/repository

Set the environment variable M2_HOME pointing to the dir where you want Maven2 installed.

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=-Dmaven.online=false
e.g. to build maven with debug info, set MAVEN_OPTS=-Dmaven.compiler.debug=true

Then run m2-bootstrap-all.bat (in Windows) or m2-bootstrap-all.sh (in Unix)

NOTE: You must run these instructions from this directory!