You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2014/01/20 00:51:49 UTC
[jira] (MNG-5533) M2 vs M3
[ https://jira.codehaus.org/browse/MNG-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-5533.
------------------------------
Resolution: Won't Fix
> 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