Hi Rene I would be delighted as a developer,and it's not really an issue for my run as I use the docker images
One thing to keep in mind is the enforcement of jigsaw modules this could be great in the long run (reduced jre.size with excluded modules) But it can also be a pain requiring passing command line arguments to enable opens required by libs. I'm not sure how bad it will be for James but at work we ended up using allopens which kinda defeats the purpose But still go, staying on an EOLed jre is bad for dev exp and operational security Jean Le lun. 6 nov. 2023 à 04:48, Rene Cordier <rcord...@apache.org> a écrit : > Hello guys, > > Well currently James is based on JDK 11. Should we think about upgrading > to at least the next LTS, JDK 17? (or why even not the current LTS, > which is the JDK 21?) I saw it being asked by a community member on a PR > a while ago (Antoine Duprat) and in our company, we would be glad for > such an upgrade as well. > > Might need a bit of work but the project could definitely benefit from > it: records (finish the long verbose POJOs), pattern matching, better GC > handling, etc. > > Would other people be interested about it too? Is it a problem for some > others in the community? > > Rene. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > >
