Am 2022-07-24 um 13:00 schrieb Maarten Mulders:
Hi all,
Allow me to chime in on this long-running discussion... I haven't raised
my voice yet, as I was curious for other opinions.
*My vote would be Java 17 for both building and running Maven 4.*
I certainly agree with the points brought up by Karl-Heinz and Benjamin
regarding Toolchains. If you really need it, you can use it. I would say
we shouldn't advise our users to use Toolchains by default; many code
bases will probably not need it. Think about all those in-house
developed applications alone, where the team knows perfectly well which
version of which JVM they will be using in production.
I would like to bring an additional point to the table. I think we all
agree we could use more people to contribute to Maven, preferably even
on a frequent basis. I have already seen multiple people getting scared
(and demotivated) by the fact that we have a huge code base which is
written with Java 7 and more recently Java 8. This means people can't
use language features that more recent versions of Java introduced, and
get discouraged by having to write code in what they experience as
"ancient" or even "pre-historic" versions of Java.
Attracting new contributors is not my main reason for voting Java 17 in
Maven 4, but it certainly plays a role for me.
While I understand these points, I don't believe that Java 17 will buy
us something substantial. We have much bigger problems than adding new
features and Java dependencies. Look into Jira, we have almost 2000 open
issues (50% are bugs), many of the years old. We have 5+ years of
technical dept components not touched, not reviewed (Tamás and me are
doing *a lot* of cleanup last couple of months). We have components
maintained by a single person for years although they are vital for the
entire ecosystem. I consider the entire discussion counterproductive.
There are maybe hipsters which would like to use records in Java code in
Maven core, but that won't solve any substantial problems except for
fanciness. At the end such moves will lead to cannibalism in the community.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
