Thanks Thomas!
I get it about Java version. And also see where you are coming from with
Maven, accordingly to your Java 24 requirement, that now makes complete
sense.
I was still using an older version of both (Java 21 and Maven 3.6), so I
had to download and install both on my machines (plus a few tweaks to
get them used), that why it took me half an hour. But now it's settled
so all is ok.
Anyway, for the first time I was able to build the code without any
issue (like even without having Docker desktop running!) and even if it
took a while, I had a working build.
I still have to understand why the build is stopping many times on my
Ubuntu machine (not the case on Mac OS), like 9 times. I had to restart
the build up to the point it was stopped (using fg). A tad annoying, but
not a big deal beside the mystery...
Thanks a lot for the explanation and for the good work with the release!
On 10/20/25 20:06, Thomas Wolf wrote:
On 20.10.25 11:00, Emmanuel Lecharny wrote:
Hi!
I would have expected Java 25 to have been the required JVM version,
and not 24, which is an intermediary version. I wonder why Java 21 is
not the requested version though.
The minimal Java version for building is 24, and maven-enforcer enforces
it. Anything lower and the Java24+-only ML-KEM class JceKEM.java at
sshd-common/src/main/java24/org/apache/sshd/common/util/security
cannot be compiled.
I don't require Java 25 because I don't want to force people to update
to Java 25 if they already are using Java 24. Since it's a _minimum_
requirement, it's OK if it is a non-LTS version. After all, a higher
LTS version exists.
Ayway, Java 25 installed locally.
I have more issue with the Maven 3.9.11 requirement.
This is making release testers a hard time. I had to spend 30 minutes
to reinstall all my env to get the build running. As much I can see
why Java in its latest version is needed, I seriously doubt an older
version of Maven is a blocker...
From https://maven.apache.org/docs/3.9.10/release-notes.html
"When running a build using Java 24 with an earlier version of Maven,
there were a lot of errors and warnings, because many dependencies
were not compatible with a Java 24 runtime.
In Maven 3.9.10 those got updated, resulting in Maven 3.9.10 now has
a far better support if you want to run your builds on Java 24."
From https://maven.apache.org/docs/3.9.11/release-notes.html
"Regression fixes and other improvements from Maven 3.9.10. All users
already on Maven 3.9.x are advised to upgrade."
So, yes, maven 3.9.11 _is_ required.
Don't know how you are set up, but for me switching maven versions is
very simple. My $PATH contains ~/bin/mvn/latest/bin, and
~/bin/mvn/latest is a symlink. I just download a new maven version,
check the download, unpack to some directory, and then point that
symlink to that directory.
That's all. Henceforth all my shells, already open or new, use the new
maven version.
Cheers,
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
