Hi Igor, That confirms the need to deprecate M2_HOME, I will remove it from installation doc first. Will need to talk to Sonatype to remove it from its book
Thanks -Dan On Wed, Jan 28, 2015 at 11:58 AM, Igor Fedorenko <[email protected]> wrote: > I see. Yes, this would be a problem. And I think there is already > similar incompatibility between maven 2.x and 3.x scripts (launcher > class name changed in 3.x). Personally, I never use M2_HOME to switch > between maven versions, so I wouldn't mind if it was removed completely. > If we want M2_HOME to work reliably, then I think we'll have to rework > mvn script to basically relaunch itself from M2_HOME/bin/mvn. > > -- > Regards, > Igor > > > On 2015-01-27 18:36, Dan Tran wrote: > >> If your changes are specific to 3.2.6, however If user has M2_HOME point >> to >> an older version MAVEN, would that be a problem? >> >> Thanks >> >> -D >> >> On Tue, Jan 27, 2015 at 3:01 PM, Igor Fedorenko <[email protected]> >> wrote: >> >> >>> >>> On 2015-01-27 17:35, Dan Tran wrote: >>> >>> My bad, it is not obvious it is from an experimental branch. However, >>>> even >>>> if this gets committed master, the configuration changes in that script >>>> may >>>> impact other distribution using M2_HOME. >>>> >>>> >>>> Can you explain how changes on that branch can impact other >>> distributions using M2_HOME? The change is not supposed to affect >>> M2_HOME in any way, so I must have overlooked something and want to >>> correct it before I propose to merge this to master. >>> >>> -- >>> Regards, >>> Igor >>> >>> >>> --------------------------------------------------------------------- >>> 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] > >
