I'll be more specific. If M2_HOME is set, then that is where the main libraries are located from (its the install directory). You can run without it, eg /some/random/install/bin/mvn and it will use /some/random/install as the home directory.
For ~/.m2 - the default location of settings.xml is ~/.m2/settings.xml, and the default local repository cache is ~/.m2/repository. The repository can be changed inside settings.xml, and settings.xml can be in either the maven installation, or passed in with --settings. So ~/.m2 is optional. In other words, everything can be changed at the command line. - Brett On 11/18/05, Jörg Schaible <[EMAIL PROTECTED]> wrote: > Leo Simons wrote on Friday, November 18, 2005 9:49 AM: > > > On Fri, Nov 18, 2005 at 12:20:39AM -0800, Bill Barker wrote: > [snip] > >> I believe that both the Maven1 and Maven2 scripts use $MAVEN_HOME, > >> which is the biggest problem with just creating a <mvn/> tag for > >> Gump2. There are also problems with separating the local Maven > >> repository between Gump1 and Gump2. As much as I hate to admit it, > >> having a <mvn/> tag in Gump2 looks like it will be a lot of work :(. > > > > Do I understand correctly that the problem you see is that > > > > -> you need different values of MAVEN_HOME > > > > -> you need different contents of ~/.maven > > Maven 1 uses MAVEN_HOME (defaults to ~/.maven) > Maven 2 uses M2_HOME (defaults to ~/.m2) > > [snip] > > - Jörg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
