Simple Java Mail's library modules still target Java 8. The CLI already targets Java 17. Since 10.0.0 is a major release, this is a good time to move the libraries to Java 11.
Java 11 lets us stop holding dependencies and build tooling back for Java 8, without forcing all library users onto Java 17. It also matches the minimum Java version for Jakarta EE 10. Anyone who still needs Java 8 can stay on Simple Java Mail 9.x.
What needs to change
- Compile every non-CLI module with
--release 11.
- Keep
cli-module on Java 17.
- Update the Maven compiler and Enforcer settings.
- Replace the JDK 8 library CI job with one that runs on a real JDK 11.
- Keep testing the full build and CLI on the newer JDKs we support.
- Make sure generated OSGi manifests require JavaSE 11 for the libraries and JavaSE 17 for the CLI.
- Update the README badge, development guide, migration notes, website, and other places that still promise Java 8 support.
- Mark 9.x as the last Java 8 line and document how we will handle critical fixes for it.
Apart from the Java requirement, this change should not alter the public API or runtime behaviour.
Simple Java Mail's library modules still target Java 8. The CLI already targets Java 17. Since 10.0.0 is a major release, this is a good time to move the libraries to Java 11.
Java 11 lets us stop holding dependencies and build tooling back for Java 8, without forcing all library users onto Java 17. It also matches the minimum Java version for Jakarta EE 10. Anyone who still needs Java 8 can stay on Simple Java Mail 9.x.
What needs to change
--release 11.cli-moduleon Java 17.Apart from the Java requirement, this change should not alter the public API or runtime behaviour.