[
https://issues.apache.org/jira/browse/BIGTOP-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082751#comment-14082751
]
Konstantin Boudnik commented on BIGTOP-1390:
--------------------------------------------
Bigtop trunk is far from flawless, as we have two troubled slaves: sles11 and
centos6. The former is more or less fixed, where the latter is likely needs to
be flush-out (my task for the weekend).
Back to your point: we are building everything with OJDK7 nowadays. There was a
discussion about it on BIGTOP-1110, IIRC. Now I am looking at
http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Oozie/ -
please disregard sles11 failures for now - and it seems to be building just
fine.
bq. since oozie enforces the requirement to 1.6
Could you be more specific on how the aforementioned enforcement is
implemented? And please pardon my ignorance with Oozie matters.
> JDK Woes
> --------
>
> Key: BIGTOP-1390
> URL: https://issues.apache.org/jira/browse/BIGTOP-1390
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.8.0
> Environment: All
> Reporter: Olaf Flebbe
>
> The Bigtop distribution cannot be build with either JDK 1.6 nor JDK 1.7
> At least solr giraph and hue have a build requirement on JDK 1.7
> On the homepage JDK 1.6 is mentioned as a requirement.
> Otherwise the Distribution cannot be build with JDK 1.7 , since oozie
> enforces the requirement to 1.6.
> A big mess.
> What scares me that the jenkins
> http://builds.apache.org/view/All/job/Bigtop-trunk/ seems to work flawless .
>
> My jenkins build needs heavy patching, how should I proceed ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
