[
https://issues.apache.org/jira/browse/BIGTOP-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092503#comment-14092503
]
Olaf Flebbe commented on BIGTOP-1390:
-------------------------------------
Because variables in bigtop.mk are not automatically propagated to the
bogtop.bom file. In fact only VERSIONS of components are propagated.
Yes, in order to get only "make" to work there is no $(eval) needed.
The other variables are propagated because of code which is triggered by an
$(eval ), a GNU make feature and by special code in the gradle file triggered
by an regexp.
I reused some of this code on order to get the code somewhat cleaner.
> 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
> Assignee: Olaf Flebbe
> Fix For: 0.8.0
>
> Attachments: jdk17.diff, oozie17_2.patch
>
>
> 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)
