@Elliotte while you are pretty right in terms of *compile* features but it ignores the biggest criteria for any ASF project : the community. Even if silly, attracting people with Java 8 is born dead today (to illustrate it just ask somebody to no more use "var" to do a PR for ex, he will start to "pfffff" ;)). So most of the challenge here is to stay an active community and not a dying one and using recent enough JDK is a good way to encourage it IMHO.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le ven. 23 févr. 2024 à 13:15, Elliotte Rusty Harold <elh...@ibiblio.org> a écrit : > On Fri, Feb 23, 2024 at 12:20 AM Robert Dean <rdea...@gmail.com> wrote: > > > That being said, if retiring Java 8 and lower output support allows > > Maven to shed technical debt and deliver improvements faster, I'd get > > over my disappointment. :) > > Given the amount of tech debt still in Maven from Maven 2 and earlier, > I don't think shifting the JDK version is likely to have any positive > impact or let improvements arise any faster. In fact, the opposite is > likely true. This is a variant of the xkcd 927 problem. > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
