My two cents, use the oldest possible jdk target and source versions that can be supported. Something like a wiki isnoften bundled with other stuff in tomcat and jumping too far might be too much.
It's worth ensuring that it will run on newer jdks but running on olders ones is still of value There's still tons of jdk8 apps out there. On Fri, Sep 19, 2025, 1:48 PM Arturo Bernal <[email protected]> wrote: > Hi all, > > > +1 to move the jakarta branch to JDK 21. > > > Why: > > > - > > Jakarta EE 11 targets Java 21; aligning reduces container friction. > - > > Virtual threads are a clear win for our I/O-bound request model and > simplify tuning. > - > > Ongoing GC/runtime improvements in 21 over 17. > > > > On Fri, 19 Sep 2025 at 5:16 PM, Jürgen Weber <[email protected]> wrote: > > > What disadvantages come with 17-only? > > > > Juan Pablo Santos Rodríguez <[email protected]> schrieb am Fr., > > 19. Sept. 2025, 11:01: > > > > > Hi Alex! > > > > > > IIRC, jakarta branch is still not merged, last commits from master > > > must be carried over there, in order to bring the jakarta branch to > > > master. After that, release should follow pretty soonish. I'll try to > > > that between this weekend and the next, if no one else beats me to it. > > > > > > Also on the topic of JDK-17, given that latest LTS is now 25, should > > > we ship the jakarta also with JDK-21 baseline? > > > > > > cheers, > > > juan pablo > > > > > > On Fri, Sep 12, 2025 at 1:40 AM Alex O'Ree <[email protected]> > wrote: > > > > > > > > Hi > > > > > > > > Is there an ETA on a JDK17 compatible release? looks like the jakarta > > > > branch was merged. that should pretty close to working on 17. > > > > > >
