Hi all, I agree this is the real question.
Moving the build to Java 17 looks reasonable and probably unavoidable at this point. Arturo On Sat, Mar 21, 2026 at 3:42 PM Gary Gregory <[email protected]> wrote: > On Sat, Mar 21, 2026 at 7:39 AM Oleg Kalnichevski <[email protected]> > wrote: > > > > On Sat, 2026-03-21 at 07:34 -0700, Ryan Schmitt wrote: > > > It looks like RAT won't get any more updates on Java 8. Should we > > > raise our > > > build-time Java requirement to 17? > > FWIW, I'm +1 to bump the runtime environment to Java 17. > > Gary > > An increasing amount of build > > > tooling is > > > dropping support for Java 8, including Maven itself (Maven 4 has to > > > run on > > > Java 17+), and Windows for ARM doesn't even *have* Java versions > > > older than > > > 17. This isn't an externally visible change, as we would still build > > > for > > > Java 8 and test on Java 8/11 JREs; it mainly involves reworking the > > > CI > > > workflows and the POM files as needed. > > > > > > > Ryan, > > > > There is a bigger question. > > > > How would you feel about dropping support for Java 8 and 11 altogether? > > Is compatibility with those JREs still important for Amazon? > > > > When do you think we could finally discontinue support for those > > versions? > > > > Oleg > > > > --------------------------------------------------------------------- > > 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] > >
