> We should target source-level support of JDK 8 too, around which you outlined > a bunch of issues around dependencies. I also found a bunch of issues around > generating documentation, site etc. I propose that we track them under the > umbrella JIRA and make progress there first.
OK. I will summarise it on HADOOP-11090. > If people want, I could setup a cut off of yetus master to run the jenkins > test-patch. (multiple maven repos, docker support, multijdk support, … ) > Yetus would get some real world testing out of it and hadoop common-dev > could stop spinning in circles over some of the same issues month after > month. ;) Thanks very much, Allen. > Seems like a step in the right direction. > Should we expect a downtime and is there a good/bad time to do this? > > Weekends are the times to work on Jenkins > do it on a saturday morning (PST) and the'res 24-48 h to stabilise before > monday morning PST. > Two days time, then? +1 > sun.security.krb5.KrbApReq was creating a static MD5 digest object and not > synchronizing access. > This has been fixed in jdk8u60. > > http://hg.openjdk.java.net/jdk8u/jdk8u60/jdk/rev/02d6b1096e89 Thank for the sharing, Kihwal. We should describe it on Wiki and documents. I'll do it based on information based on this thread. Thanks, - Tsuyoshi On Thu, Oct 15, 2015 at 11:57 PM, Steve Loughran <ste...@hortonworks.com> wrote: > >> On 15 Oct 2015, at 14:42, Karthik Kambatla <ka...@cloudera.com> wrote: >> >> On Wed, Oct 14, 2015 at 4:28 PM, Allen Wittenauer <a...@altiscale.com> wrote: >> >>> >>> If people want, I could setup a cut off of yetus master to run the jenkins >>> test-patch. (multiple maven repos, docker support, multijdk support, … ) >>> Yetus would get some real world testing out of it and hadoop common-dev >>> could stop spinning in circles over some of the same issues month after >>> month. ;) >>> >> >> Seems like a step in the right direction. >> >> Should we expect a downtime and is there a good/bad time to do this? > > > > Weekends are the times to work on Jenkins > > do it on a saturday morning (PST) and the'res 24-48 h to stabilise before > monday morning PST. > > Two days time, then?
