[jira] [Closed] (MNGSITE-508) Maven Install Instructions could set an alias instead of altering the path on Unix-based OS's

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNGSITE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MNGSITE-508.
----------------------------------
    Resolution: Won't Fix

Tips have been removed.

> Maven Install Instructions could set an alias instead of altering the path on Unix-based OS's
> ---------------------------------------------------------------------------------------------
>
>                 Key: MNGSITE-508
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-508
>             Project: Maven Project Web Site
>          Issue Type: Improvement
>            Reporter: Glen Peterson
>            Priority: Minor
>
> At the bottom of this page:
> [https://maven.apache.org/install.html]
> It suggests adding to PATH:
>  
> {code:java}
> export PATH=/opt/apache-maven-3.9.0/bin:$PATH{code}
>  
> I'm only familiar with Linux, but is it really necessary to make mvn the first thing on the path?  I'd suggest instead:
> {code:java}
> # in ~/.profile
> export MVN_HOME=/opt/apache-maven-3.9.0/bin{code}
> and
>  
> {code:java}
> # in ~/.bash_aliases
> alias mvn='$MVN_HOME/bin/mvn'{code}
>  
> This should have a very similar effect for CLI usage but not force every bash command to search the mvn bin directory before any other directories.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)