maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Idan Bidani (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5533) M2 vs M3
Date Tue, 03 Dec 2013 15:23:45 GMT

    [ https://jira.codehaus.org/browse/MNG-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336697#comment-336697
] 

Idan Bidani commented on MNG-5533:
----------------------------------

M3_HOME name is not good because it will require the same discussion on maven 4(if there will
be).
If any change should take place it should be MVN_HOME like Michael suggests. The version should
not be part of the var name
                
> 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

Mime
View raw message