We just start the progress moving to JDK 11 slow and hard at work. Maybe pekko 1.2.x should be a good start for JDK 11? FYI: The graphql-java project is still on JDK 8, caffeine requires jdk 11 from 3.x and 2.9.x is still on jdk 8; project reactor-core is using multiple-release for Loom support.
何品 Matthew de Detrich <[email protected]> 于2023年7月15日周六 18:28写道： > > Not sure how representative this is, but, at least one of the > organizations I work for, a large European bank, still relies on Java 8 for > all their production deployments. > Although this is something they will eventually do, migrating to a newer > version of Java is not something they can easily do and will take them > years. > So, if the Java 8 support is dropped, they'll have to renounce porting > their application to Pekko and stick to Akka 2.6. > > While my view is that dropping JDK 8 support for 1.1.x is too soon, > supporting JDK 8 for many many years is also going to be a tough > proposition (this has to ultimately be decided upon by rhe community). > > I don't know how much influence you have in this, but I would recommend > migrating as soon as possible. JDK 8 is already at EOL support unless you > use Oracle/Amazon JDK and the longer people are stuck on JDK 8 the greater > risk it has of creating a split in the user base (I.e. JDK 8 will become > its own language/environment because everyone else has already moved on to > later JDKs which are increasingly getting newer features which Pekko will > want to use at some point). > > Note that Pekko is open source, so nothing is preventing companies > maintaining their own fork of Pekko that maintains JDK 8 support while > pulling in upstream changes. I don't normally advocate for forks, but if we > get to the point that only one or two companies out of the entire community > are using JDK 8 and everyone else has moved on, this is the most fair > outcome in regards to maintenance burden. > > On Fri, 14 July 2023, 19:43 David Massart, <[email protected]> wrote: > > > All, > > > > Not sure how representative this is, but, at least one of the > > organizations I work for, a large European bank, still relies on Java 8 > for > > all their production deployments. > > Although this is something they will eventually do, migrating to a newer > > version of Java is not something they can easily do and will take them > > years. > > So, if the Java 8 support is dropped, they'll have to renounce porting > > their application to Pekko and stick to Akka 2.6. > > > > Best regards, > > > > David > > > > > On Jul 14, 2023, at 10:20, Nicolas Vollmar <[email protected]> wrote: > > > > > > Even Java 11 is quite old by now. Installing multiple JDK versions is > > also not that big of a problem. > > > I'd agree for moving forward to Java 11 since Java 8 is getting really > > old. > > > > > >> On 14 Jul 2023, at 17:23, PJ Fanning <[email protected]> wrote: > > >> > > >> Hi everyone, > > >> > > >> Is there any appetite for abandoning Java 8 support in Pekko 1.1.0? > > >> > > >> An example discussion: > > >> > > >> https://github.com/apache/incubator-pekko/discussions/482 > > >> > > >> There is also a complication in our MIME checks due to Java 8. > > >> > > >> https://github.com/apache/incubator-pekko/pull/481 > > >> > > >> I'm usually quite reluctant to move away from supporting legacy Java > > >> versions but maybe it's time to start dropping Java 8 support. Java 8 > > >> users can stick with Pekko 1.0.0. > > >> > > >> Does anyone have any thoughts on this? > > >> > > >> Regards, > > >> PJ > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
