You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2019/12/26 22:09:00 UTC
[jira] [Assigned] (MNG-6456) Log $JAVA_HOME when there is an issue
with it
[ https://issues.apache.org/jira/browse/MNG-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylwester Lachiewicz reassigned MNG-6456:
-----------------------------------------
Assignee: (was: Sylwester Lachiewicz)
> Log $JAVA_HOME when there is an issue with it
> ---------------------------------------------
>
> Key: MNG-6456
> URL: https://issues.apache.org/jira/browse/MNG-6456
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
> Affects Versions: 3.5.4
> Reporter: Johanneke Lamberink
> Priority: Minor
> Fix For: 3.7.x-candidate
>
>
> I've just spend more time than was necessary on debugging a problem where Maven complained about a missing $JAVA_HOME, because there was no logging of which $JAVA_HOME was used.
> It would be really helpful to be able to see the $JAVA_HOME being used by Maven, in addition to the current logging:
>
> {noformat}
> 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{noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)