Repository navigation
Require Java 17 (LTS) #708
Description
Describe the question / problem (required)
As per https://www.oracle.com/java/technologies/java-se-support-roadmap.html
11 (LTS) Premier Support Until September 2023.
Maybe the plugin should require Java 17?
Context (optional)
No response
Activity
TheSnoozer commentedon Mar 20, 2024
As per https://maven.apache.org/docs/history.html
maven
4.0.0-alpha-13now requiresJava 17[-]Require 17 (LTS)[/-][+]Require Java 17 (LTS)[/+]elharo commentedon Jul 22, 2024
Please don't. We are using this with Java 8. I expect others are too.
Also note that Oracle != Java. Java 8 is fully supported by multiple vendors
TheSnoozer commentedon Jul 22, 2024
Maven 4.X is requiring Java 17 so this (breaking)change will eventually happen, not sure when.
Certainly there is IMHO the following to consider:
Whenever it is happening needs to evaluate what the best new version would be....I guess as this is a maven plugin following maven makes sense and enforcing java 17 eventually...
elharo commentedon Jul 22, 2024
But Maven 3.9 is continuing, and I expect many projects will stick with that for compatibility reasons. Java 8 will go away eventually but not for multiple years yet.
scrobbleme commentedon Feb 6, 2025
Is there any serious reason to still stick to Java 8 for the build prozess...? You can use a modern Java and still build for 8...
+1 for upgrading to Java 17. Escpecially with the (hopefully soon) release of Maven 4 ...
elharo commentedon Feb 6, 2025
There are incompatibilities. One I recently noticed was that jdeprscan 17 can't analyze java 8.
scrobbleme commentedon Feb 7, 2025
(No offense meant, I'm just curious)
Thanks for the example, but isn't this more like a "once in a lifetime" command?
If you are still using Java 8 and still need to scan for deprecations regularly... doesn't sound like the typical blocker for a Maven plugin like this ;)
elharo commentedon Feb 7, 2025
That's just the most recent thing I found. There's a lot of others, and likely others I've not yet noticed. There's very good reason for many shops and projects to stay on java 8 specifically given what Sun/Oracle did in Java 9+.
TheSnoozer commentedon Feb 8, 2025
Ok let me explain: This ticket is here to *eventually move this plugin to Java 17. I'm well aware that there is more than "just" oracle who provides a version/variant of java, but even those other variants will stop to be supported at some point in the future. Therefore I can't comment when java 17 will be required, but at some point it will happen and should happen as some of the plugin's dependency already require a more recent java version (e.g. see git-commit-id/git-commit-id-plugin-core#172). Maybe when it's time to do this I will no longer have the time/motivation to maintain this project so maybe this update will never happen.
TDLR: I acknowledge that users still want and need this plugin to function with java 8. Eventually the plugin will be updated to java 17 - if your project still requires java 8 you can simply use an older version of the plugin...it's your choice. But eventually (maybe in 3 years or some time in the future) the plugin will drop java 8.