Grails

Auto discover of JAVA_HOME

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 1.3.6
  • Fix Version/s: 2.3-M2
  • Component/s: None
  • Labels:
    None
  • Environment:
    Linux, Ubuntu
  • Patch Submitted:
    Yes

Description

When JAVA_HOME is not set (but java command is in the PATH) then grails command (startGrails script actually) stops at message "JAVA_HOME environment variable is not set".
I don't want to explicitly set JAVA_HOME variable because I manage my JDK instances by update-java-alternatives in Ubuntu. It switches system wide JDK, but does not set the JAVA_HOME variable. If I would set JAVA_HOME manually then any changes made by update-java-alternatives would not be reflected in JAVA_HOME which is obviously incorrect.

However startGrails script can be improved, so that it can guess JAVA_HOME. Actually Groovy startup script does it very well, so I moved auto-discovery code from groovy script to startGrails and made pull request at Github

Activity

People

  • Assignee:
    Unassigned
    Reporter:
    Maciej Mazur
Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Last Reviewed: