[
https://issues.apache.org/jira/browse/MNG-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386539#comment-17386539
]
Robert Scholte commented on MNG-7010:
-------------------------------------
Actually, I think we should drop the line completely.
To run Maven you will need {{java}}.
If one wants to compile java code, you will need {{javac}}, which is a
requirement for the maven-compiler-plugin and not Maven.
If one wants to generate java documentation, you will need {{javadoc}}, which
is a requirement for the maven-javadoc-plugin and not Maven.
When you are using toolchains, or have the path to the JDK specified otherwise,
JRE is enough to run Maven.
It it is not a Java project, JRE is enough to run Maven.
I think the plugins already do these checks, otherwise they should, but having
a JDK instead or JRE doesn't have to be a Maven requirement.
> 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)
