incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (Commented) (JIRA)" <>
Subject [jira] [Commented] (BIGTOP-25) Standardize JAVA_HOME detection
Date Tue, 18 Oct 2011 00:05:10 GMT


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.

> Standardize JAVA_HOME detection
> -------------------------------
>                 Key: BIGTOP-25
>                 URL:
>             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/
to guess at a good JVM to use if JAVA_HOME isn't set. For example, if both OpenJDK and Oracle
JDK are installed, 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:!default.jspa
For more information on JIRA, see:


View raw message