maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Commented] (MNG-5423) mvn shell script doesn't always export JAVA_HOME
Date Mon, 30 Nov 2015 23:49:11 GMT


Michael Osipov commented on MNG-5423:

[~jvanzyl], do you remember in which commit you have fixed this one? I cannot find anything
in master while grepping git log for this jira issue. The fix version obviously does not require
Maven 4.x.

> mvn shell script doesn't always export JAVA_HOME
> ------------------------------------------------
>                 Key: MNG-5423
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 3.0.4, 3.1.0-alpha-1
>            Reporter: Thomas Mueller
>             Fix For: Issues to be reviewed for 4.x
> There are code paths through the mvn shell script that do not result in JAVA_HOME being
exported if it is not set when entering the script. 
> I found this in 3.0.4 on MacOS X. JAVA_HOME gets set at line 117, but then is never exported,
so the java process doesn't get the value. Based on reading the code, I see other paths through
the script where JAVA_HOME is not exported even though it gets set by the script. 
> On the head, there are statements like the following (line 65):
> export JAVA_HOME=/System/Library/Java/JavaVirtualMachines/CurrentJDK/Contents/Home
> This is not valid /bin/sh syntax.  /bin/sh does not allow the export to be on the same
line where the environment variable is set. There are also paths on the head where JAVA_HOME
is not exported when it is set. 

This message was sent by Atlassian JIRA

View raw message