Hi!

I have no strong preference on either 17 or 21. Last time we discussed it,
IIRC, consensus was on 17, but I was wondering if there was appetite for
upgrading to 21, given that 25 is out now.

For me 21 means more features, but it's totally fine for me to stay on
JDK-17. Similar question could be asked for the  tomcat version, but I can
imagine the general feeling :-) If there is no real need of newer versions,
staying a bit behind means more actual places where JSPWiki can be deployed.


Cheers,
juan pablo


El vie, 19 sept 2025, 19:48, Arturo Bernal <[email protected]> escribió:

> 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.
> > >
> >
>

Reply via email to