[
https://issues.apache.org/jira/browse/MNG-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386681#comment-17386681
]
Robert Scholte commented on MNG-7010:
-------------------------------------
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}
> Omit "NB: JAVA_HOME should point to a JDK not a JRE" except when that is the
> problem
> ------------------------------------------------------------------------------------
>
> Key: MNG-7010
> URL: https://issues.apache.org/jira/browse/MNG-7010
> Project: Maven
> Issue Type: Improvement
> Reporter: Elliotte Rusty Harold
> Assignee: Michael Osipov
> Priority: Minor
> Fix For: 4.0.x-candidate, 3.8.x-candidate
>
>
> Got this message a bunch today:
>
> $ mvn verify
> The JAVA_HOME environment variable is not defined correctly
> This environment variable is needed to run this program
> NB: JAVA_HOME should point to a JDK not a JRE
>
> fair enough. My JAVA_HOME is broken, for reasons. However the problem is
> **not** that it points to a JDK instead of a JRE. Maven should omit "NB:
> JAVA_HOME should point to a JDK not a JRE" except when that is the problem.
> Also, I have no idea what NB means here. Nota bene perhaps?
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
