[
https://issues.apache.org/jira/browse/BIGTOP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Mahé updated BIGTOP-25:
-----------------------------
Attachment: 0001-BIGTOP-25.-Add-a-new-bigtop-utils-package-which-prov.patch
Here is a patch to add a new package named bigtop-utils and which will provide
some java autodetection code.
Some notes:
* I replaced along the way some Cloudera URLs by some BigTop ones
* I had to enhance the build system so we can build packages which don't have
source tarball
* it put the script on /usr/libexec on RPM and /usr/lib/bigtop-utils on debs
(debian does not have /usr/libexec)
packages were built on fedora and maverick
> 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: Bruno Mahé
> Priority: Minor
> Fix For: 0.2.0
>
> Attachments:
> 0001-BIGTOP-25.-Add-a-new-bigtop-utils-package-which-prov.patch,
> bigtop-javahome
>
>
> 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