You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org> on 2012/03/05 18:35:59 UTC
[jira] [Updated] (BIGTOP-373) bigtop-detect-javahome not
customizable
[ https://issues.apache.org/jira/browse/BIGTOP-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-373:
------------------------------------
Fix Version/s: 0.4.0
0.3.0
> bigtop-detect-javahome not customizable
> ---------------------------------------
>
> Key: BIGTOP-373
> URL: https://issues.apache.org/jira/browse/BIGTOP-373
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.3.0
> Reporter: Philip Zeyliger
> Assignee: James Page
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-373.patch, BIGTOP-373.patch
>
>
> The following snippet is in {{bigtop-packages/src/common/bigtop-utils/bigtop-detect-javahome}}:
> {code}
> # Uncomment and set the following variable in order for the
> # guesswork step to be skipped
> #
> # JAVA_HOME=/usr/java/latest
> {code}
> In a packaged world, however, bigtop-detect-javahome will be overridden with every subsequent release of bigtop. Defaults and configurations like this might go into /etc/default/bigtop or perhaps /etc/bigtop/..., so that users can configure permanently to enable or disable JAVA_HOME detection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira