AFAIR it is the class worlds config that actually pulls out the environment variable to set up the classpath, so the only thing that would happen is you would be using a different class worlds from the one in the home... In any case M2_HOME trumps MAVEN_HOME so if the scripts were not updated then it is all moot anyways
On Friday, 28 June 2013, Jörg Schaible wrote: > Stephen Connolly wrote: > > > MAVEN_HOME is for Maven. > > > > If M2_HOME is set, then that will be used by Maven 2+ and MAVEN_HOME will > > be ignored. > > Well, then download M305 and have a look into the start scripts. MAVEN_HOME > is nowhere found, while M2_HOME is anywhere used. > > > 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 > > Nevertheless, you still don't have to set it. It's done automatically in > the > start script. > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] <javascript:;> > For additional commands, e-mail: [email protected]<javascript:;> > > -- Sent from my phone
