MAVEN_HOME is for Maven.

If M2_HOME is set, then that will be used by Maven 2+ and MAVEN_HOME will
be ignored.

When Maven 3 was being initially released we were going to drop M2_HOME
completely, but decided to keep support for it.

Going forward, I would just pick MAVEN_HOME and ensure M2_HOME is unset as
we do not have M3_HOME nor will we have M4_HOME so we will be reclaiming
MAVEN_HOME as the recommendation

On Friday, 28 June 2013, Jörg Schaible wrote:

> Nayana ABREU wrote:
>
> > In relation to the installation of Maven on Windows, when I add the
> > Variable in the Systems Variables.... I saw some examples in which users
> > type M2_HOME for the variable name, is it a problem if I typed
> > *MAVEN_HOME*for variable name? In summary, I want to know if the name
> > for variable name
> > is an arbitrary thing or if it has an exactly defined name.
> >
> > Thanks,
>
> MAVEN_HOME was for Maven 1.
>
> Actually I don't set M2_HOME at all, because it is setup internally in the
> Maven start scripts. That way I can easily switch between different Maven
> 2/3 versions just by calling the appropriate start script.
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] <javascript:;>
> For additional commands, e-mail: [email protected]<javascript:;>
>
>

-- 
Sent from my phone

Reply via email to