Re: Re : Upgrade James to JDK17?
Hi, It seems the community in general is in favor of migrating to JDK 21! For this I created an issue on the JIRA board: https://issues.apache.org/jira/browse/JAMES-3961 To answer some people with concerns or sharings in the thread: - Wojtek: we also run our version of James on JDK17 now. But having the code base following up would be clearly better :) - Jean: I believe we just ended up using allopens as well on our side too. Dunno much about those jigsaw modules and how complex it could be to switch to this but it could be worth trying - Karsten: to the question should we maintain at least for the next version of James a JDK 11 version in parallel, I'm less sure. I feel it's probably the better way, but the resources on development aren't that big, it would put more pressure on the devs to maintain 2 code bases simultaneously. I'm not personally in favor TBH (but maybe the community is willing to make this effort). Thanks and best regards, Rene. On 11/6/23 20:37, Karsten Otto wrote: +1 for JDK 21. I think the module enforcement may have quite an architectural impact though. Maybe we should have a separate James version 3.9 or even 4.0 for a clean cut? Cheers, Karsten On 06.11.23 6:42 AM, Benoit TELLIER wrote: +1 for JDK 21. Thanks for the proposal. -- Best regards, Benoit TELLIER General manager of Linagora VIETNAM. Product owner for Team-Mail product. Chairman of the Apache James project. Mail: btell...@linagora.com Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal) Le nov. 6, 2023 4:47 AM, de Rene Cordier 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 - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Re: Re : Upgrade James to JDK17?
+1 for JDK 21. I think the module enforcement may have quite an architectural impact though. Maybe we should have a separate James version 3.9 or even 4.0 for a clean cut? Cheers, Karsten On 06.11.23 6:42 AM, Benoit TELLIER wrote: +1 for JDK 21. Thanks for the proposal. -- Best regards, Benoit TELLIER General manager of Linagora VIETNAM. Product owner for Team-Mail product. Chairman of the Apache James project. Mail: btell...@linagora.com Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal) Le nov. 6, 2023 4:47 AM, de Rene Cordier 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 smime.p7s Description: S/MIME cryptographic signature
Re: Upgrade James to JDK17?
Definitely good idea. For what it's worth, we already run James on JDK17 (it was finally possible after getting rid of serialization library a while back; probably jump to JDK21 would be fine as well right now). From building point of view (thus enforcing minimal JDK to be run on) - I don't see why anyone would still would want to stick with version 11. Java picked up speed and it's a good thing. Wojtek On 06/11/2023 04:46, Rene Cordier wrote: 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 - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Re: Re : Upgrade James to JDK17?
+1 for JDK 21 Regards, Quan Vào Th 2, 6 thg 11, 2023 vào lúc 16:22 Eugen Stan đã viết: > +1 for JDK 21 > > La 06.11.2023 07:42, Benoit TELLIER a scris: > > > > +1 for JDK 21. > > > > Thanks for the proposal. > > > > -- > > > > Best regards, > > > > Benoit TELLIER > > > > General manager of Linagora VIETNAM. > > Product owner for Team-Mail product. > > Chairman of the Apache James project. > > > > Mail: btell...@linagora.com > > Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal) > > > > > > Le nov. 6, 2023 4:47 AM, de Rene Cordier 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 > > > > > > > > > > > - > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > >
Re: Re : Upgrade James to JDK17?
+1 for JDK 21 La 06.11.2023 07:42, Benoit TELLIER a scris: +1 for JDK 21. Thanks for the proposal. -- Best regards, Benoit TELLIER General manager of Linagora VIETNAM. Product owner for Team-Mail product. Chairman of the Apache James project. Mail: btell...@linagora.com Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal) Le nov. 6, 2023 4:47 AM, de Rene Cordier 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 - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Re : Upgrade James to JDK17?
+1 for JDK 21. Thanks for the proposal. -- Best regards, Benoit TELLIER General manager of Linagora VIETNAM. Product owner for Team-Mail product. Chairman of the Apache James project. Mail: btell...@linagora.com Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal) Le nov. 6, 2023 4:47 AM, de Rene Cordier 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
Re: Upgrade James to JDK17?
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 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 > >
