[
https://jira.codehaus.org/browse/MNG-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336684#comment-336684
]
Martin Spamer commented on MNG-5533:
------------------------------------
This doesn't break _backwards_ compatibility, because you can retain an M2
setting as well as having M3 in the environment. The cost in time to add M3 is
trivial compared to having to repeatedly swap from one configuration to the
other. So the reward vastly outweights the cost (time to change once vs
multiple swapping).
MAJOR.MINOR.PATCH from http://apr.apache.org/versioning.html
My suggestion is completely within the apache versioning strategy, since the
MAJOR release 2 -> 3 is already a compatibility breaking and is arguable
alllowed for a MINOR release which allows addition of new constants M3 and
essentially deprecating (but not removing) M2
> M2 vs M3
> --------
>
> Key: MNG-5533
> URL: https://jira.codehaus.org/browse/MNG-5533
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Class Loading, Command Line, Documentation: General,
> General
> Affects Versions: Issues to be reviewed for 3.x
> Environment: Windows
> Reporter: Martin Spamer
> Priority: Critical
>
> Maven 3 uses the M2 environment variable. Surely it would be more reasonable
> to update this to M3 to allow sensible migration. e.g
> M2=C:\Program Files\Apache Software Foundation\apache-maven-2.2.1\bin
> M2_HOME=C:\Program Files\Apache Software Foundation\apache-maven-2.2.1
> M3=C:\Program Files\Apache Software Foundation\apache-maven-3.1.1\bin
> M3_HOME=C:\Program Files\Apache Software Foundation\apache-maven-3.1.1
> MAVEN=%M2% or MAVEN=%M3%
> PATH=%MAVEN%;%PATH%
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
