Hi, On 19.07.22 18:34, Anders Hammar wrote:
I'd say Java 11 if there isn't some very good feature in Java 17 that we need. So far we have supported the current and prior Java LTS version and I think that's a good aim.
I see several options to improve the code: * sealed-class which makes it easier to keep internals really internal... * switch-expressions * named instanceof * var (Type inference yes exists already in JDK 11 or more accurate since JDK10). > Lot's of users are still on Java 11 and
even if you can execute Maven with a different Java version than you build for, it does add some complexity.
If you like to build code for JDK 8 you can simply use --release 8 (maven.compiler.release) ...is much easier than toolchains. So no problem if you run with JDK 17 you do the same...and getting performance improvements for free... Furthermore But a lot of them will be forced in some areas for example with Spring / Spring Boot 3.0.0 ... JDK17 is minimum...
But, if we don't release it until Sept 2023 I think Java 17 is fine (as Java 23 should be out). :-)
I hope that we could get a version out this year...
On Tue, Jul 19, 2022 at 6:24 PM Karl Heinz Marbaise <khmarba...@gmx.de <mailto:khmarba...@gmx.de>> wrote: Hi to all, what do you think about using JDK17 as minimum requirement for running the future Apache Maven 4.0.0 ? Kind regards Karl Heinz Marbaise --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org <mailto:dev-unsubscr...@maven.apache.org> For additional commands, e-mail: dev-h...@maven.apache.org <mailto:dev-h...@maven.apache.org>
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
