Hi Julian, Thanks for the transparency. That helps a lot in these discussions. Is there any timeline on when the downstream project is ready for Java 21?
Given that Oracle premier support for Java 17 is expiring in Sept. 2026 I expect this to happen this year, right? Thanks, Konrad > On 7. Jan 2026, at 11:42, Julian Reschke <[email protected]> wrote: > > Am 07.01.2026 um 10:31 schrieb Robert Munteanu: >> ... >> What is the reason for switching straight to Java 21 instead of 17? >> Keep in mind that we were on Java 11 for a long time and did not see >> any major drawbacks. >> IMO Oak (and Sling) are building blocks for applications and should >> have wider compatibility with Java versions as opposed to applications >> that can choose to run only on the latest Java version. >> ... > > Unfortunately we currently have a downstream project which is still on Java > 17. Moving to Java 21 (right now) would force us to have an additional > maintenance branch for some time, so I'd prefer to avoid that. > > And yes, once that problem is gone, we should move on to Java 21 (or even > further). > > Best regards, Julian >
