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 (Commented) (JIRA)" <ji...@apache.org> on 2011/10/18 02:05:10 UTC

[jira] [Commented] (BIGTOP-25) Standardize JAVA_HOME detection

    [ https://issues.apache.org/jira/browse/BIGTOP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129360#comment-13129360 ] 

Roman Shaposhnik commented on BIGTOP-25:
----------------------------------------

Solving this in its full glory is very important but unlikely for 0.2.0. Thus I'm looking for a Bigtop-level solution 
to unblock our package installation (currently all sorts of things fail because we simply can't do anything without
JAVA_HOME being set).

Now, as for Bigtop here's what I would like to propose: we take the attached code and put it into the post-install 
phase of our packages. This code will either find Java and update and explicit setting of JAVA_HOME in an 
appropriate /etc/default/foo file or it will issue a warning during package installation telling user to do it.

Thoughts?
                
> Standardize JAVA_HOME detection
> -------------------------------
>
>                 Key: BIGTOP-25
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-25
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>            Priority: Minor
>             Fix For: 0.2.0
>
>
> The Hadoop packages go through some effort (see /usr/lib/hadoop-0.20/bin/hadoop-config.sh) to guess at a good JVM to use if JAVA_HOME isn't set. For example, if both OpenJDK and Oracle JDK are installed, hadoop-config.sh will choose Oracle every time. Other packages that Bigtop integrates, don't follow the same practice (ZK, Pig, etc.). It would be nice to have this common code shared.

--
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