[ http://jira.codehaus.org/browse/MNG-2376?page=comments#action_68008 ]
David Smiley commented on MNG-2376:
-----------------------------------
On Darwin (Mac OS X), alter the mvn.sh script such that JAVA_VERSION is not
consulted at all if JAVA_HOME is specified.
For example, like so (not tested):
{{
if [ -z "$JAVA_HOME" ] ; then
if [ -z "$JAVA_VERSION" ] ; then
JAVA_VERSION="CurrentJDK"
else
echo "Using Java version: $JAVA_VERSION"
fi
JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/${JAVA_VERSION}/Home
fi
}}
Additionally... you might want the Java code that handles mvn -v to output the
Java version in effect, in addition to the Maven version.
> Have Java code output Java version, not the shell script
> --------------------------------------------------------
>
> Key: MNG-2376
> URL: http://jira.codehaus.org/browse/MNG-2376
> Project: Maven 2
> Type: Improvement
> Components: Command Line
> Versions: 2.0.4
> Environment: Mac OS X 10.4
> Reporter: David Smiley
> Priority: Minor
> Fix For: 2.2
>
>
> The shell script outputs $JAVA_VERSION. In my case, in an ill-fated attempt
> to get maven to use JDK 1.4, this was set to 1.4 but JAVA_HOME was already
> set (in .profile or wherever) to that of the current JDK (1.5). So it is
> inconsistent and led me on a wild goose chase to track down a problem. If
> Maven is going to output the java version, do it from java code using the
> right system property. Only use JAVA_VERSION to help select a JAVA_HOME, if
> JAVA_HOME isn't set.
> Perhaps there is some standard approach to this sort of thing but I am unsure.
--
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
