Off the top of my head I know all the packages are built with java8 right now, so those tests would fail. I don't think there's any of it that is too difficult, it's just going to be a lot of little things that are probably easier to do in one pass instead of two.
Kind Regards, Brandon On Mon, Aug 29, 2022 at 4:25 PM Blake Eggleston <beggles...@apple.com> wrote: > > Can you say some more about what extra work you expect removing jdk8 to > cause? I'd expect removing jdk8 to be mostly subtractive (from build.xml and > circleci confs), and jdk17 support to be mostly additive. > > We're getting ready to merge the first set of accord integration patches, and > the accord library requires java11+. My understanding is that jdk17 support > in C* is still several months away, so if we can avoid making one a > dependency on the other, that would be preferable. > > > On Aug 29, 2022, at 2:01 PM, Brandon Williams <dri...@gmail.com> wrote: > > +1 for removing it when we add 17, to avoid making extra work. > > Kind Regards, > Brandon > > On Mon, Aug 29, 2022 at 3:40 PM Blake Eggleston <beggles...@apple.com> wrote: > > > Sorry, I meant trunk, not 4.1 :) > > On Aug 29, 2022, at 1:09 PM, Blake Eggleston <beggles...@apple.com> wrote: > > Hi all, I wanted to propose removing jdk8 support for 4.1. Active support > ended back in March of this year, and I believe the community has built > enough confidence in java 11 to make it an uncontroversial change for our > next major release. Let me know what you think. > > Thanks, > > Blake > > >