I really like the idea. This might also need to go in hand with plugins, the compiler "release" argument is the way to go and this will require removing completely the maven.compiler.source and maven.compiler.target.
Compiling to an older release is the easy part, yet the only thing that might be a pain is when you want to test with an older release, toolchains might help but if that is not simplified then it will create a lot of friction for users, even right now is not so easy to build with one JDK and test with many, assuming you build for Java 8, you might want to test with Java 8, Java 11, Java 17, and even Java 19-ea, right now it's more a build and test with the same JDK, it's not a big deal when you can build and test with older releases, but it will be problematic when you build with a new release and test with an old release. On Tue, Jul 19, 2022 at 6:25 PM Karl Heinz Marbaise <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 > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
