Hello, thanks Jorge I fully support your summary.
want to bring an additional points in support for newer runtime Java: Because Maven alone isn’t the complete ecosystem and many other tools have higher requirements already. Fr example both Jenkins (maven-style jobs) as well as SonarQube scanner plugins can’t be used with Java 8 anymore. And yes such a shift was not only for those big tech-Gigants which are stuck on Java8 a pain, but also for many other users - but this is in the past. Most have migrated to be finally able to use the -release option as a quality of life improvement even though they have to target Java 8 Bytecode level. I think there is absolutely no problem to move along with a new major version of maven, in fact it’s the only sane moment to do so. I am sure many plug-in authors are eager to raise their minimum version just to be able to use new external technologies. And if the whole ecosystem understands there is a 3.d and 4.x branch, the better… Gruss Bernd Jorge Solórzano wrote on 24. Feb 2024 23:42 (GMT +01:00): > Hi Maven Developers, > > A lot has been told already from both sides, but please, please, let's > focus on how to improve the current status and define how and what Java > version will be required for Maven, not on trivial discussions about using > var or virtual threads. — https://bernd.eckenfels.net --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
