+1 on changing the defaults, but it seems we should be at least building with JDK6.
Enis On Mon, Dec 9, 2013 at 2:55 PM, lars hofhansl <[email protected]> wrote: > Maybe for 0.94 we should do both after all. > There will be installations out there with JDK 6 and we should make sure > we do not break anything there. > > I'll set up an additional full build for 0.94 based on JDK 7. > > -- Lars > > > > ________________________________ > From: Jean-Marc Spaggiari <[email protected]> > To: dev <[email protected]>; lars hofhansl <[email protected]> > Sent: Monday, December 9, 2013 4:01 AM > Subject: Re: Default JDK settings for Jenkins projects > > > So if we move 0.94 in JDK 7, I guess we all agree there is no reason to > keep trunk in JDK 6, right? Then we should all allign to JFK 7? > > JM > > > > 2013/12/8 lars hofhansl <[email protected]> > > > JDK 6 was EOL'd Feb 2013. Even premium support runs out this month. > > Apparently there is an extended support option until Dec 2016. > > > > Not sure who in their right mind would run a production system on JDK 6 > > going forward. Even we (Salesforce) switched wholesales to JDK 7 > (including > > HBase 0.94), and we're extremely conservative due to the uptime sensitive > > nature of our service. > > > > > > We should switch the 0.94 builds over to JDK 7. > > Unless I hear strong/good reasons I'll do that and see what fails and > then > > fix the issues. > > > > -- Lars > > > > > > > > ________________________________ > > From: Ted Yu <[email protected]> > > To: "[email protected]" <[email protected]> > > Sent: Sunday, December 8, 2013 5:52 PM > > Subject: Re: Default JDK settings for Jenkins projects > > > > > > There're several test failures when running 0.94 test suite using jdk 1.7 > > > > So there is some work to be done before switching to jdk 1.7 for 0.94 > > > > Cheers > > > > > > > > On Mon, Dec 9, 2013 at 9:41 AM, Jean-Marc Spaggiari < > > [email protected] > > > wrote: > > > > > Make sens to have trunk with JDK 7 too... But I'm not sure for 0.94... > > It's > > > mainly running in prod with JDK 6. So not sure we can align them all... > > > > > > > > > 2013/12/8 Andrew Purtell <[email protected]> > > > > > > > I think all builds should be running JDK 7. I don't want to be only > > > chasing > > > > JDK 7 related test issues on the 0.98 build alone. > > > > > > > > > > > > On Mon, Dec 9, 2013 at 9:27 AM, Jean-Marc Spaggiari < > > > > [email protected] > > > > > wrote: > > > > > > > > > I agree. We should build 0.98 against JDK 7 instead of 6. JDK 6 End > > of > > > > > Public Updates since to February 2013. 0.98 is planned for 2014. > Will > > > be > > > > a > > > > > year after that. So I think it's time to move to JDK 7. > > > > > > > > > > My opinion ;) > > > > > > > > > > JM > > > > > > > > > > > > > > > 2013/12/8 Andrew Purtell <[email protected]> > > > > > > > > > > > I was looking for differences between the trunk and 0.98 builds > > since > > > > > > Jenkins projects for the former are passing while the latter are > > not. > > > > > Seems > > > > > > the trunk jobs are set up to use "JDK 1.6 (latest)" while the > 0.98 > > > > builds > > > > > > are set up to use "JDK 1.7 (latest)". For the time being I have > set > > > the > > > > > > 0.98 builds to also use JDK 6 to see if their results will mirror > > > trunk > > > > > > afterward. > > > > > > > > > > > > However, I think we should be using JDK 7 or OpenJDK 7 to run all > > of > > > > our > > > > > > builds 0.96+. What do you think? > > > > > > > > > > > > -- > > > > > > Best regards, > > > > > > > > > > > > - Andy > > > > > > > > > > > > Problems worthy of attack prove their worth by hitting back. - > Piet > > > > Hein > > > > > > (via Tom White) > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > > > > > - Andy > > > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > > Hein > > > > (via Tom White) > > > > > > > > > >
