I'd like to resume this discussion about switching master to require JDK 17.
These past days, I've been working on improving the usage of toolchains (first inside maven, but now completely in the maven-toolchains-plugin) with [1]. If we want to go further, we could simplify the selection by modifying the POM somehow to add a specific section, but I suspect most people will just use the release flag on the compiler to target bytecode. The only downside I see, beyond the additional configuration (though the goal is that users don't really have to generate/maintain the toolchains) is that the selection of the toolchain is done during the build, so that JDK profile based activation can not be used. Note that the use of environment variables is also another way to work around, for example in github [2]. I think with those improvements, requiring JDK 17 for master should be doable. Any concerns of suggestions ? Cheers, Guillaume [1] https://github.com/apache/maven-toolchains-plugin/pull/14 [2] https://github.com/B3Partners/kadaster-gds2/blob/b0cd5c392bc1f48dec11c83c828254a868264467/.github/ubuntu-toolchains.xml Le mar. 19 juil. 2022 à 18:25, Karl Heinz Marbaise <khmarba...@gmx.de> a écrit : > 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 > > -- ------------------------ Guillaume Nodet
