Thank you Konrad for that good catch! I'll try to review your PR this evening.
Indeed the intention was to target Java 1.8 and it is a bug that it is actually Java-11.
The reason for this lower target and the reason why I think that we should not require Java-17 for the Maven runtime is that it would require a Java-17 JRE to launch a Maven build using the embedded runtime.
Maven 3.8.8 requires Java 1.7 (Maven 3.9 is planned to be Java 1.8) and due to other dependencies M2Es Maven runtime already requires Java 1.8.
But lifting that further to Java-17 just for one additional class of M2E, that obviously can be done with Java 1.8, IMHO is hardly to justify against users that only want to use the standard Maven plugins.
Of course one can still compile against older Java versions in the build, but since we don't gain much in lifting the bar I think we should not make it more complicated to our users for now.
If there are better reasons in the Future I'm open to discuss that again, but now I think it is not worth it.
Gesendet: Freitag, 25. November 2022 um 14:03 Uhr
Von: "Mickael Istria" <mistria@xxxxxxxxxx>
An: "Maven Integration for Eclipse developers mailing list" <m2e-dev@xxxxxxxxxxx>
Betreff: Re: [m2e-dev] M2E's Maven-Runtime projects reworked
As said maven-runtime should use Java 1.8, rest of m2e uses Java 17.
Why not making the runtime use Java 17 as well?
_______________________________________________ m2e-dev mailing list m2e-dev@xxxxxxxxxxx To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/m2e-dev
