We don't want JDK 8 only code going into branch-2 line. Moving Jenkins to 1.8 
right-away will shield such code, how do we address that?

Thanks,
+Vinod

On Apr 21, 2015, at 5:54 PM, Robert Kanter <rkan...@cloudera.com> wrote:

> Sure, I'll try to change the Jenkins builds to 1.8 first.
> 
> On Tue, Apr 21, 2015 at 3:31 PM, Andrew Wang <andrew.w...@cloudera.com>
> wrote:
> 
>> Hey Robert,
>> 
>> As a first step, could we try switching all our precommit and nightly
>> builds over to use 1.8? This is a prerequisite for HADOOP-11858, and safe
>> to do in any case since it'll still target 1.7.
>> 
>> I'll note that HADOOP-10530 details the pain Steve went through switching
>> us to JDK7. Might be some lessons learned about how to do this transition
>> more smoothly.
>> 
>> Thanks,
>> Andrew
>> 
>> On Tue, Apr 21, 2015 at 3:15 PM, Robert Kanter <rkan...@cloudera.com>
>> wrote:
>> 
>>> + yarn-dev, hdfs-dev, mapred-dev
>>> 
>>> On Tue, Apr 21, 2015 at 3:14 PM, Robert Kanter <rkan...@cloudera.com>
>>> wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> Moving forward on some of the discussions on Hadoop 3, I've created
>>>> HADOOP-11858 to set the minimum version of Hadoop 3 to JDK 8.  I just
>>>> wanted to let everyone know in case there's some reason we shouldn't go
>>>> ahead with this.
>>>> 
>>>> thanks
>>>> - Robert
>>>> 
>>> 
>> 

Reply via email to