[
https://issues.apache.org/jira/browse/JAMES-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792092#comment-17792092
]
Benoit Tellier commented on JAMES-3961:
---------------------------------------
Mailing list discussions (for record):
https://www.mail-archive.com/[email protected]/msg16880.html
I opened a draft pull request on this topic:
https://github.com/apache/james-project/pull/1833
Apparently, in order to work with Java 21, maven plugin that works with code
needs to be updated. I needed to update maven-plugin-plugin for mailetdoc
plugin to 3.10.2.
I also encountered errors on the openjpa plugin:
https://issues.apache.org/jira/browse/OPENJPA-2918 likely needs an update too
but that one is in the hand of the OpenJPA team.
> 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: [email protected]
For additional commands, e-mail: [email protected]
