You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Andrew Purtell <ap...@apache.org> on 2013/12/09 02:17:59 UTC
Default JDK settings for Jenkins projects
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)
Re: Default JDK settings for Jenkins projects
Posted by Ted Yu <yu...@gmail.com>.
One thing puzzling me is that although JDK 1.7 is configured for QA runs,
JDK 1.6 is used.
e.g. from https://builds.apache.org/job/PreCommit-HBASE-Build/8107/console :
/home/jenkins/tools/java/latest
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode)
On Tue, Dec 10, 2013 at 8:06 AM, Enis Söztutar <en...@gmail.com> wrote:
> +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 <la...@apache.org> 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 <je...@spaggiari.org>
> > To: dev <de...@hbase.apache.org>; lars hofhansl <la...@apache.org>
> > 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 <la...@apache.org>
> >
> > > 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 <yu...@gmail.com>
> > > To: "dev@hbase.apache.org" <de...@hbase.apache.org>
> > > 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 <
> > > jean-marc@spaggiari.org
> > > > 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 <ap...@apache.org>
> > > >
> > > > > 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 <
> > > > > jean-marc@spaggiari.org
> > > > > > 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 <ap...@apache.org>
> > > > > >
> > > > > > > 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)
> > > > >
> > > >
> > >
> >
>
Re: Default JDK settings for Jenkins projects
Posted by Enis Söztutar <en...@gmail.com>.
+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 <la...@apache.org> 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 <je...@spaggiari.org>
> To: dev <de...@hbase.apache.org>; lars hofhansl <la...@apache.org>
> 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 <la...@apache.org>
>
> > 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 <yu...@gmail.com>
> > To: "dev@hbase.apache.org" <de...@hbase.apache.org>
> > 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 <
> > jean-marc@spaggiari.org
> > > 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 <ap...@apache.org>
> > >
> > > > 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 <
> > > > jean-marc@spaggiari.org
> > > > > 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 <ap...@apache.org>
> > > > >
> > > > > > 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)
> > > >
> > >
> >
>
Re: Default JDK settings for Jenkins projects
Posted by lars hofhansl <la...@apache.org>.
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 <je...@spaggiari.org>
To: dev <de...@hbase.apache.org>; lars hofhansl <la...@apache.org>
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 <la...@apache.org>
> 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 <yu...@gmail.com>
> To: "dev@hbase.apache.org" <de...@hbase.apache.org>
> 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 <
> jean-marc@spaggiari.org
> > 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 <ap...@apache.org>
> >
> > > 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 <
> > > jean-marc@spaggiari.org
> > > > 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 <ap...@apache.org>
> > > >
> > > > > 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)
> > >
> >
>
Re: Default JDK settings for Jenkins projects
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
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 <la...@apache.org>
> 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 <yu...@gmail.com>
> To: "dev@hbase.apache.org" <de...@hbase.apache.org>
> 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 <
> jean-marc@spaggiari.org
> > 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 <ap...@apache.org>
> >
> > > 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 <
> > > jean-marc@spaggiari.org
> > > > 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 <ap...@apache.org>
> > > >
> > > > > 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)
> > >
> >
>
Re: Default JDK settings for Jenkins projects
Posted by lars hofhansl <la...@apache.org>.
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 <yu...@gmail.com>
To: "dev@hbase.apache.org" <de...@hbase.apache.org>
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 <jean-marc@spaggiari.org
> 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 <ap...@apache.org>
>
> > 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 <
> > jean-marc@spaggiari.org
> > > 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 <ap...@apache.org>
> > >
> > > > 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)
> >
>
Re: Default JDK settings for Jenkins projects
Posted by Ted Yu <yu...@gmail.com>.
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 <jean-marc@spaggiari.org
> 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 <ap...@apache.org>
>
> > 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 <
> > jean-marc@spaggiari.org
> > > 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 <ap...@apache.org>
> > >
> > > > 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)
> >
>
Re: Default JDK settings for Jenkins projects
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
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 <ap...@apache.org>
> 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 <
> jean-marc@spaggiari.org
> > 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 <ap...@apache.org>
> >
> > > 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)
>
Re: Default JDK settings for Jenkins projects
Posted by Andrew Purtell <ap...@apache.org>.
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 <jean-marc@spaggiari.org
> 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 <ap...@apache.org>
>
> > 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)
Re: Default JDK settings for Jenkins projects
Posted by Ted Yu <yu...@gmail.com>.
bq. I think we should be using JDK 7 or OpenJDK 7
+1
On Mon, Dec 9, 2013 at 9:27 AM, Jean-Marc Spaggiari <jean-marc@spaggiari.org
> 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 <ap...@apache.org>
>
> > 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)
> >
>
Re: Default JDK settings for Jenkins projects
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
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 <ap...@apache.org>
> 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)
>
Re: Default JDK settings for Jenkins projects
Posted by Stack <st...@duboce.net>.
On Sun, Dec 8, 2013 at 5:17 PM, Andrew Purtell <ap...@apache.org> wrote:
> 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.
>
>
0.96 is 1.7 as is hadopoqa.
> However, I think we should be using JDK 7 or OpenJDK 7 to run all of our
> builds 0.96+. What do you think?
>
Yes. I thought that was the tendency. I'd set 0.98 that way copying 0.96.
I did not realize trunk still on jdk6.
Thanks,
St.Ack
Re: Default JDK settings for Jenkins projects
Posted by Stack <st...@duboce.net>.
On Sun, Dec 8, 2013 at 5:17 PM, Andrew Purtell <ap...@apache.org> wrote:
> 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.
>
>
0.96 is 1.7 as is hadopoqa.
> However, I think we should be using JDK 7 or OpenJDK 7 to run all of our
> builds 0.96+. What do you think?
>
Yes. I thought that was the tendency. I'd set 0.98 that way copying 0.96.
I did not realize trunk still on jdk6.
Thanks,
St.Ack