[
https://issues.apache.org/jira/browse/JAMES-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier resolved JAMES-3961.
---------------------------------
Resolution: Fixed
We migrated to java 21
> 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
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
