[
https://issues.apache.org/jira/browse/STORM-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980192#comment-13980192
]
ASF GitHub Bot commented on STORM-295:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/incubator-storm/pull/85#issuecomment-41325810
I would prefer the .ini file. In general I would like to see most of the
config coming from storm.yaml, but I realize in this case it is a bit of a
chicken and egg problem because we need to use JAVA_HOME to run the code to
pull the configs out of storm.yaml.
> Add storm configuration to define JAVA_HOME
> -------------------------------------------
>
> Key: STORM-295
> URL: https://issues.apache.org/jira/browse/STORM-295
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Reporter: Suresh Srinivas
>
> Currently storm uses either /usr/bin/java (most likely) or java pointed to by
> PATH.
> Storm requires a way to define JAVA_HOME in configuration. This will simplify
> pointing to a version of java that a cluster admin or test frameworks intend
> to use for storm, especially in an environments where multiple versions of
> java is on the cluster nodes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
