Jonathan, I have also been hearing JDK 7 more these days.(or less about JDK6?) For example Open JDK 7 is default on those OSs.
Centos 7 http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7#head-b02657cf2e223edb2d7946cbc45086d42c2bb41b Ubuntu 14.04 (this is LTS) http://packages.ubuntu.com/trusty/devel/default-jdk Maybe I'm looking into OSs that the Ambari community is not keen on. Then what are the OS versions we are targeting? I will ask my PM and share the answer with you guys. Once we have a JDK version we like, then we can put the version into our Docker solution and are good to go (of course, This will be a whole new thing and have you all review my POC and we will start form there) On Fri, Oct 17, 2014 at 7:52 PM, Jonathan Hurley <[email protected]> wrote: > Hi Jun, > > Thanks for the reply and discussion about this issue. > > I disagree about the JDK version remaining at JDK 7. Although it might be > true that JDK 8 is the latest version with JDK 9 on the horizon, many of > the commodity machines that run Ambari are probably better equipped to run > JDK 6. As long as we say Ambari supports JDK 6, I think the continuous > integration environment must reflect JDK 6 compatibility. With JDK 7 as the > build runtime, we cannot possibly enforce that compatibility. > > As far as the environment on b.a.o, some of the other jobs that I looked > at are built using JDK 1.6.0_20. I think it would probably be simple enough > for Ambari to be built with the same job parameters. I don’t have any > problem with Ambari being installed on a machine with JDK7+, but for > continuous integration builds and tests, it seems like the least common > denominator (python 2.6 and JDK6) are the right choices. > > With all of that said, docker integration with Jenkins seems like an > interesting idea and I would look forward to seeing a discussion of the > benefits it would give the development community. > > On Oct 17, 2014, at 10:36 PM, jun aoki <[email protected]> wrote: > > > Jonathan, thank you for raising an important point, and this matters a > lot > > to my next proposal. > > > > In terms of JDK versions, knowing that Oracle has put their mainstream > JDK > > as version 1.8 (1), I'm slightly toward to 1.7 which is closer to 1.8, > but > > I'm open to either version and let the community vote to it. > > > > What is my next proposal? > > I have been testing Ambari build on Docker (2) and would like to propose > it > > as the trunk and branch commit build once I complete a POC. > > > > Slaves on builds.a.o have a lot of limitations in terms of what > environment > > you want (at least as far as I know) but Docker will enable us to use > > whatever environment we like to support. > > > > > > (1) 1.8 is the top list in this download page > > http://www.oracle.com/technetwork/java/javase/downloads/index.html > > > > (2) > > > https://builds.apache.org/view/A-D/view/Ambari/job/Ambari-trunk-Commit-docker/ > > > > > > On Fri, Oct 17, 2014 at 2:37 PM, Erin Boyd <[email protected]> wrote: > > > >> Agreed +1 to JDK1.6 and Python 2.6 > >> > >> ----- Original Message ----- > >> From: "Yusaku Sako" <[email protected]> > >> To: [email protected] > >> Sent: Friday, October 17, 2014 2:27:59 PM > >> Subject: Re: Apache Builds & JDK > >> > >> +1 on JDK 1.6, Python 2.6. > >> > >> On Fri, Oct 17, 2014 at 1:26 PM, Nate Cole <[email protected]> > wrote: > >> > >>> +1 for JDK 1.6 - I see this as the same reasoning we went with python > 2.6 > >>> vs 2.7. > >>> > >>> > >>> On Oct 17, 2014, at 4:22 PM, Jonathan Hurley <[email protected]> > >>> wrote: > >>> > >>>> Hi All, > >>>> > >>>> I introduced a failure on builds.apache.org today; the odd thing was > >>> that the failing test ran perfectly fine on my local environment and on > >>> other developer’s environments. It was a failure in a mock library and > I > >>> determined it was caused by a JDK version difference. I use JDK 1.6 and > >>> builds.apache.org uses JDK 1.7 > >>>> > >>>> This raises an important question: If Ambari supports JDK 1.6, we > >> should > >>> be building with JDK 1.6 in order to catch compilation issues? I could > >>> easily introduce a JDK 1.7 method or class and builds.apache.org won’t > >>> catch it. > >>>> > >>>> I’m going to work on fixing my unit test now that I can see it failing > >>> after switching to JDK 1.7, but I think we need to change > >>> builds.apache.org to JDK 1.6. > >>>> > >>>> Community thoughts? > >>>> -- > >>>> CONFIDENTIALITY NOTICE > >>>> NOTICE: This message is intended for the use of the individual or > >> entity > >>> to > >>>> which it is addressed and may contain information that is > confidential, > >>>> privileged and exempt from disclosure under applicable law. If the > >> reader > >>>> of this message is not the intended recipient, you are hereby notified > >>> that > >>>> any printing, copying, dissemination, distribution, disclosure or > >>>> forwarding of this communication is strictly prohibited. If you have > >>>> received this communication in error, please contact the sender > >>> immediately > >>>> and delete it from your system. Thank You. > >>> > >>> > >>> -- > >>> CONFIDENTIALITY NOTICE > >>> NOTICE: This message is intended for the use of the individual or > entity > >> to > >>> which it is addressed and may contain information that is confidential, > >>> privileged and exempt from disclosure under applicable law. If the > reader > >>> of this message is not the intended recipient, you are hereby notified > >> that > >>> any printing, copying, dissemination, distribution, disclosure or > >>> forwarding of this communication is strictly prohibited. If you have > >>> received this communication in error, please contact the sender > >> immediately > >>> and delete it from your system. Thank You. > >>> > >> > >> -- > >> CONFIDENTIALITY NOTICE > >> NOTICE: This message is intended for the use of the individual or > entity to > >> which it is addressed and may contain information that is confidential, > >> privileged and exempt from disclosure under applicable law. If the > reader > >> of this message is not the intended recipient, you are hereby notified > that > >> any printing, copying, dissemination, distribution, disclosure or > >> forwarding of this communication is strictly prohibited. If you have > >> received this communication in error, please contact the sender > immediately > >> and delete it from your system. Thank You. > >> > > > > > > > > -- > > -jun > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. > -- -jun
