Hi Andriy, Thanks!
And I don’t think we need to worry about JDK9 failure a lot since JDK9 is EOL now. Could we also setup build job for JDK11(IIRC we need EasyMock 3.7-SNAPSHOT for JDK11[1])? Since JDK11 is the LTS version I believe we should target to support this version mainly. [1]https://github.com/easymock/easymock/issues/218 <https://github.com/easymock/easymock/issues/218> Best Regards －－－－－－－－－－－－－ Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat > On Sep 22, 2018, at 2:19 AM, Andriy Redko <[email protected]> wrote: > > Hey guys, > > It's been a while since we had the last more or less successful build on > Jenkins for JDK9+. I have made a few > changes (hopefuly temporary) to let the builds going: > > - for JDK9+ profile, changed EasyMock 3.7-SNAPSHOT to 3.6 (since snapshot is > not available, 3.6 is JDK10 ready) > - for JDK9+ profile, changed the codegen-plugin/jdk-cxf-with-toolchain > integration test to use the toolchain from the current JDK it is being built > with > > The JDK10 build is looking good now > https://builds.apache.org/job/CXF-Master-JDK10/284/console, for JDK9 the > toolchain is still failing > https://builds.apache.org/job/CXF-Master-JDK9/ (I am looking into it). If > someone has any concerns or ideas, please share. > > Thanks! > > Best Regards, > Andriy Redko > > >
