Thanks Dan for getting JDK11 support done!! Would we need to coordinate changes for downstream projects which use core repo and move them to JDK11? Or can it be done in phased manner where core repo can be built using both JDK8 and JDK11 such that downstream project which are currently built using JDK8 can still compile it and gradually switched to JDK11
And would standalone jar built using JDK11 can still be used with JDK8? As class file version is still at 1.8 level it may be possible but would be useful to confirm this prior to release core repo. >From runtime perspective I think G1GC (default with JDK 11) should be fine for our usage and we need not tweak the default settings with switch to JDK11 Chetan Mehrotra On Fri, Nov 1, 2019 at 12:37 AM Matt Sicker <boa...@gmail.com> wrote: > I'm surprised extra dependencies aren't required. When we added > support for Java 11 in Jenkins, we had to add some auto-installed > modules to replace some Java SE APIs that aren't part of java.base and > require implementations. > > On Thu, 31 Oct 2019 at 10:09, dan McWeeney <mcwee...@adobe.com.invalid> > wrote: > > > > There has been talk previously about moving to later java and scala > versions. I’ve got this all working in a PR[0], which passes travis. I was > wondering if there is some further testing that people think should be done. > > > > -dan > > > > [0] - https://github.com/apache/openwhisk/pull/4706 > > > > > -- > Matt Sicker <boa...@gmail.com> >
