[jira] [Resolved] (OODT-567) show JAVA_HOME env var in RADiX start command in all cases

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OODT-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann resolved OODT-567.
------------------------------------
    Resolution: Won't Fix

nice to have, but no time

> show JAVA_HOME env var in RADiX start command in all cases
> ----------------------------------------------------------
>
>                 Key: OODT-567
>                 URL: https://issues.apache.org/jira/browse/OODT-567
>             Project: OODT
>          Issue Type: Bug
>          Components: radix
>    Affects Versions: 0.5
>            Reporter: Andrew Hart
>            Assignee: Andrew Hart
>            Priority: Minor
>             Fix For: 1.1
>
>
> The RADiX deployment script prints out a list of the environment variables when it starts up. This looks something like: 
> {code}
> user@foo ~/Development/sandbox/oodt-deploy/bin $ ./oodt start
> Using OODT_BASE:   /home/user/Development/sandbox/oodt-deploy
> Using OODT_HOME:   /home/user/Development/sandbox/oodt-deploy
> Using OODT_TMPDIR: /home/user/Development/sandbox/oodt-deploy/temp
> Using JRE_HOME:    /usr
> Using CLASSPATH: 
> {code}
> A common startup problem is related to JAVA_HOME not being properly set on the target system. Currently, the RADiX script only includes the JAVA_HOME value if the the "oodt" command is run with the debug flag. To make it easier to immediately diagnose potential environment problems, the value for JAVA_HOME should be displayed in all modes of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)