I’m confused by what you wrote, and not going to spend my time looking for
parallels on logo-dev. IIUC the vote was clearly for moving to java 21, but due
to some reasoning in the -1 votes this was rejected: since then a bunch of
people have objected to failing the vote. Specifically, which resu
I was also thinking the ability of a community to vote and move forward
with whatever the result
is more important than the result itself. Disputing *this* vote slows
getting to the next one.
Its not even the kind of vote that would change the direction of the
project.
Delany
On Fri, 23 May 2025
There is an interesting parallel here with the what is happening in the
logo-dev mailing list: Someone calls for a vote, the results are obvious
(count the votes), then it feels like we are back to square one when some
starts haggling the whole thing over again. This might not be a bad thing,
we ar
I do not think we can use that as a point otherwise we should go with java
8.
So question is really do we go with what is current when we do the final or
do we go with a past choice assuming people not upgrading their stack will
upgrade their stack cause maven 4 is too awesome to not upgrade.
Roma
On Fri, May 23, 2025, 13:40 Benjamin Marwell wrote:
> Hey, I can totally understand the people voting -1 for the given reasons.
> Even with Java 17 support ending in ~15 months FOR PERSONAL USE.
> There will be a loong tail of extended support for money.
>
And how much of this moooney w
Hey, I can totally understand the people voting -1 for the given reasons.
Even with Java 17 support ending in ~15 months FOR PERSONAL USE.
There will be a loong tail of extended support for money.
Anyway, my suggestion:
Let's do Maven 4.0.0 with Java 17.
Wait for a 4.0.1, 4.1.0... and then wit
-1 for release, +1 for rc4.
Reason: What Sylwester said, plus Nikita from JetBrains asking nicely.
They (JB) would love to see API stability so they can ship an IntelliJ
IDEA release in time with Maven 4.
This of course applies to all other IDEs.
Nikita is on #maven in slack, maybe also subscribed
