[
https://issues.apache.org/jira/browse/BIGTOP-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089427#comment-14089427
]
Konstantin Boudnik commented on BIGTOP-1390:
--------------------------------------------
Olaf, any change you can take it one step away to implement the full solution,
where JDK_VERSION is set in the bigtop.ml file. The it will be automatically
propagated into a special file {{bigtop.bom}} which gets created for every
package build and gets sourced into {{do-component-build}}. At this point you
will be able to use
{code}
${WORKDIR}/bin/mkdistro.sh -DjavaVersion=${JDK_VERSION} ...
{code}
instead of the currently hard-coded one. Thanks!
BTW, you don't need to remove previous versions of the patches as it - as a
general rule - helps to preserve the history of the discussion and gradual
improvements.
> 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
> Attachments: 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)
