Il lun 1 ott 2018, 17:00 Sijie Guo <guosi...@gmail.com> ha scritto: > +1 on dropping java9 and supporting java 11 > > Just one comment, I remember there was a performance penalty in netty using > java 9, you have to turn some flags on. Is that still true on using java > 11? >
You are talking about io.netty.tryReflectionSetAccessible. This is not changed as far as I know. In latest Netty version, released last week I saw there are a bunch of improvements on this topic, that is to not trigger IllegalAccess warning on stdout, but I did not check. Enrico > Sijie > > On Mon, Oct 1, 2018 at 7:22 AM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > Hi, > > I am working on support for JDK11 at build time and in tests > > > > this is the master issue > > https://github.com/apache/bookkeeper/issues/1710 > > > > This email is to discuss about dropping CI jobs for JDK9. > > JDK9 is really obsolete, I think no one will ever use it in production. > > > > I am running i production on JDK10 in some sites and BookKeeper works > very > > well. > > > > My proposal is to drop JDK9 jobs in favour of JDK11. > > > > When can also add JDK12-EA jobs at least on Travis-CI. > > > > In general I think that we should support JDK8, JDK11 (new LTS??) and > > latest release OpenJDK > > > > > > Thoughts ? > > > > Cheers > > Enrico > > > -- -- Enrico Olivelli
