Michael Osipov created MNG-7195:
-----------------------------------
Summary: Rework JAVA_HOME handling
Key: MNG-7195
URL: https://issues.apache.org/jira/browse/MNG-7195
Project: Maven
Issue Type: Task
Components: Command Line
Reporter: Michael Osipov
Fix For: 4.0.x-candidate
Coming from
[here|https://issues.apache.org/jira/browse/MNG-7010?focusedCommentId=17386681&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17386681].
[~rfscholte] says:
It is not needed anymore to set JAVA_HOME.
If it is set, %JAVA_HOME%/bin/java should be used to start Maven, otherwise
java should be picked up from the PATH.
This should be explained on the [install
page|https://maven.apache.org/install.html].
With this we can assume that JAVA_HOME was set on purpose, but misconfigured.
I suggest to have a message like:
{noformat}
The JAVA_HOME environment variable is not defined correctly, so Apache Maven
cannot be started.
JAVA_HOME is set to "<actual value>", but "%JAVA_HOME%/bin/java" does not exist.
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
