[
https://issues.apache.org/jira/browse/JAMES-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17785435#comment-17785435
]
Benoit Tellier commented on JAMES-3961:
---------------------------------------
> Should we switch our modules to Jigsaw modules?
- Now that attributes serialization no longer relies on FST (and no longer
allows arbitrary deserialisation) we *could* try to better enforce Java modules.
> Should we maintain a JDK11 version in parallel for letting time for everybody
> to do the switch?
-1
James is still a moving project. We can announce that James 3.8.x is the last
Java 11 compatible branch, and offer support for it.
> Migrate code base to JDK21
> --------------------------
>
> Key: JAMES-3961
> URL: https://issues.apache.org/jira/browse/JAMES-3961
> Project: James Server
> Issue Type: Improvement
> Reporter: René Cordier
> Priority: Major
> Fix For: 3.9.0
>
>
> The community seems in favor of adopting JDK 21 and migrating the code base
> to it. Multiple reasons for it:
> * JDK 11 reached officially EOLÂ
> * JDK 21 is the latest LTS
> * multiple new features like records (bye bye boilerplates on POJOs),
> pattern matching, better GC, better thread management, ...
> Few things to keep in mind as well:
> * should we switch our modules to Jigsaw modules?
> * should we maintain a JDK11 version in parallel for letting time for
> everybody to do the switch?
> How:
> * ADR explaining the change
> * switch the JDK to 21 in the code base
> * modify the code to get a green build with minimal changes first
> * update documentation accordingly
> * can refactoring things little by little after (like switching to records
> for POJOs for example)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
