Benjamin Marwell ☕Feb 28, 2024

I might have started something... 🤭

#java17 #java21 @ASFMavenProject

Apache Maven 4 might require Java 17...

Show threadDeven PhillipsFeb 28, 2024
@bmarwell
I approve!
@ASFMavenProject @sparsick
Show threadBenjamin Marwell ☕

@infosec812
Thanks! Depending on the time line of Maven 4, we even might bump it to Java 21... But that's nowhere near final, only single voices so far.

The biggest problem is actually to explain that:
1. Maven 3.9.x will work for a while
2. Even with Maven on JDK21, you can still use -release=7
3. Even with Java 22, you can use toolchains to build with just any JDK.

@ASFMavenProject @sparsick

Feb 28, 2024 at 8:55pmWeb
Show threadBenjamin Marwell ☕Feb 28, 2024

@infosec812
We call those people "aligners" - those who want to align the Maven runtime with the compiler and the target runtime.

Often there's little to no advantage in that.

@ASFMavenProject @sparsick

Show threadjoschiFeb 28, 2024

@bmarwell
Re 2: No you can't (without using another JDK <20 via toolchains). https://inside.java/2022/09/26/quality-heads-up/

@infosec812 @ASFMavenProject @sparsick

Quality Outreach Heads-up - JDK 20 - Support for 1.7 source and target removed from javac – Inside.java

This Heads-Up is part of the regular communication sent to the projects involved, it covers a change in javac in JDK 20 …

Show threadKarl Heinz Marbaise (he/him)Feb 29, 2024
@joschi @bmarwell @infosec812 @ASFMavenProject @sparsick JDK 21 supports --release 8 but already with WARNINGs... Java 7 is not supported anymore ...
Show threadBenjamin Marwell ☕Feb 29, 2024

@khmarbaise
You're both right, JDK17 is last which supports seven.

Still good enough and nowhere near a blocker imo.

@joschi @infosec812 @ASFMavenProject @sparsick

×
Benjamin Marwell ☕Feb 28, 2024

I might have started something... 🤭

#java17 #java21 @ASFMavenProject

Apache Maven 4 might require Java 17...

Show threadDeven PhillipsFeb 28, 2024
@bmarwell
I approve!
@ASFMavenProject @sparsick
Show threadBenjamin Marwell ☕Feb 28, 2024

@infosec812
Thanks! Depending on the time line of Maven 4, we even might bump it to Java 21... But that's nowhere near final, only single voices so far.

The biggest problem is actually to explain that:
1. Maven 3.9.x will work for a while
2. Even with Maven on JDK21, you can still use -release=7
3. Even with Java 22, you can use toolchains to build with just any JDK.

@ASFMavenProject @sparsick

Show threadBenjamin Marwell ☕Feb 28, 2024

@infosec812
We call those people "aligners" - those who want to align the Maven runtime with the compiler and the target runtime.

Often there's little to no advantage in that.

@ASFMavenProject @sparsick

Show threadjoschiFeb 28, 2024

@bmarwell
Re 2: No you can't (without using another JDK <20 via toolchains). https://inside.java/2022/09/26/quality-heads-up/

@infosec812 @ASFMavenProject @sparsick

Quality Outreach Heads-up - JDK 20 - Support for 1.7 source and target removed from javac – Inside.java

This Heads-Up is part of the regular communication sent to the projects involved, it covers a change in javac in JDK 20 …

Show threadKarl Heinz Marbaise (he/him)Feb 29, 2024
@joschi @bmarwell @infosec812 @ASFMavenProject @sparsick JDK 21 supports --release 8 but already with WARNINGs... Java 7 is not supported anymore ...
Show threadBenjamin Marwell ☕Feb 29, 2024

@khmarbaise
You're both right, JDK17 is last which supports seven.

Still good enough and nowhere near a blocker imo.

@joschi @infosec812 @ASFMavenProject @sparsick

Show threadRobertFeb 28, 2024
@bmarwell @ASFMavenProject yes!
Show threadMarcus FihlonFeb 29, 2024
@bmarwell @ASFMavenProject If a project is still being developed today with #Java 7 or older and the maintainers do not want to switch to a newer Java version, I can hardly imagine that the maintainers will consider switching to #Maven 4. Therefore, the new major version of Maven, which will have incompatibilities anyway, would be a good opportunity to switch to the then current LTS as a minimum requirement.
Show threadBenjamin Marwell ☕Feb 29, 2024

@McPringle
> which will have incompatibilities anyway,

Actually, as long as you use 3.x-plugins only (and don't remove the version from the parent declaration), you can use both Maven 3 and 4 for the same project.

@ASFMavenProject

Show threadMarcus FihlonMar 1, 2024
@bmarwell @ASFMavenProject For real world projects with dozens of plugins and a complex configuration I'm skeptical. Maybe I'll be positively surprised, but I plan for a lot of testing and incompatibilities.
Show threadMichael BienMar 3, 2024
@bmarwell @ASFMavenProject Congrats on the successful vote!
Looking forward to maven 4 on JDK 17+  #java #maven