You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2014/06/19 23:51:26 UTC
[jira] [Commented] (BIGTOP-1335) JAVA_HOME auto detect improvement
[ https://issues.apache.org/jira/browse/BIGTOP-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037953#comment-14037953 ]
Konstantin Boudnik commented on BIGTOP-1335:
--------------------------------------------
Another possible improvement is to add alternatives check to the list of current test?
> JAVA_HOME auto detect improvement
> ---------------------------------
>
> Key: BIGTOP-1335
> URL: https://issues.apache.org/jira/browse/BIGTOP-1335
> Project: Bigtop
> Issue Type: Improvement
> Components: Init scripts
> Reporter: Guo Ruijing
>
> In existing implementation, JAVA_HOME is automatically detected in /usr/lib/bigtop-utils/bigtop-detect-javahome if JAVA_HOME is not configured. If some component configure JAVA_HOME and some component doesn't configure JAVA_HOME by mistake, different component may use different JAVA_HOME. In this case, it is not easy to find JAVA_HOME difference in different components.
> We may improve:
> 1. WARNING message is generated if JAVA_HOME is not configured in /usr/lib/bigtop-utils/bigtop-detect-javahome.
> or 2. We may disable JAVA_HOME auto detection and use JAVA_HOME from /etc/default/bigtop-utils
--
This message was sent by Atlassian JIRA
(v6.2#6252)