[ http://jira.codehaus.org/browse/MNG-2121?page=all ]
John Casey updated MNG-2121:
----------------------------
Fix Version: 2.2
> mvn launch script should use jpackage.org config if available
> -------------------------------------------------------------
>
> Key: MNG-2121
> URL: http://jira.codehaus.org/browse/MNG-2121
> Project: Maven 2
> Type: Improvement
> Components: Command Line
> Versions: 2.0.2
> Environment: GNU/Linux
> Reporter: Chris Hubick
> Priority: Minor
> Fix For: 2.2
> Attachments: maven_jpp.patch
>
>
> I am attempting to install and use Maven for the first time... so excuse me
> if I'm off base here :)
> It is my understanding that a single global classpath (and JVM) is generally
> deprecated, so I trivially modified my version of the command line 'mvn'
> script to automatically utilize my existing jpackage.org configuration (patch
> attached).
> Also, the installation instructions at http://maven.apache.org/download.html
> say to unpack it to /usr/local/maven-2.0.2/, yet the mvn script looks for the
> existance of /opt/m2/ when attempting to automatically set $M2_HOME. I
> symlinked /usr/local/maven to /usr/local/maven-2.0.2, and also trivially
> patched my mvn script to look for /usr/local/maven/ when setting $M2_HOME.
> Instead of adding $M2_HOME/bin to my global path, I just symlinked
> /usr/local/bin/mvn -> /usr/local/maven/bin/mvn. In this way, I have a
> working Maven (I hope) without having to modify any global configuration on
> my machine - meaning the install should be side effect free. I can also
> upgrade to a new release without having to modify any configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
