On Tue, Jul 19, 2022 at 7:52 PM Karl Heinz Marbaise <khmarba...@gmx.de> wrote: > > Hi, > > On 19.07.22 19:44, Jorge Solórzano wrote: > > 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. > > No they should not removed because the javac does not remove it either. > > For example it cases where you like to write your test with JDK 17 but > your target will be JDK 8...it makes sometimes sense.. >
I might be missing something but that scenario could be handled by setting maven.compiler.testRelease to JDK 17 and maven.compiler.release to JDK 8. Fair enough, they can remain just for backward compatibility, but even if javac does not remove it, it doesn't mean that are useful having --release, and there are probably more for backward compatibility than anything else, again, this is just to drop legacy baggage. > > > > 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, > > If I would run my build with JDK 17 and --release 8. > > Why should I test with Java 8, 11 and 17 or more accurate what should I > test? Think of an app that targets Java 8, if you build with Java 17 (even targeting Java 8), you might want to test (unit test, etc.) using the Java 8 *runtime* to ensure that everything works as expected. > > > 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. > > What should being tested here? > For example JUnit Jupiter is doing that for a very long time. Not sure what are you referring to, taking into account that JUnit Jupiter is using Gradle. > > > > > > > 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
