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.

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...


That being said, let's run the build ;-)

On 10/19/25 13:31, Thomas Wolf wrote:
Hello,

our journey towards a 3.0.0 release of Apache MINA SSHD continues.

I've staged a candidate for a new milestone pre-release 3.0.0-M2.
Please review and vote!

The focus in this milestone was on cryptographic algorithms:

* Refactor and simplify the way algorithms are resolved.
* Simplify handling of ed25519 keys/signatures.
* Make sshd-common and sshd-osgi multi-release JARs.
* On Java 11+: use the built-in ChaCha20.
* On Java 15+: use the built-in ed25519.
* On Java 24+: use the built-in ML-KEM.

Minimum requirements for building have been bumped: you need
Java >= 24 and Maven >= 3.9.11. The runtime minimum requirement
is unchanged at Java 1.8.

For the full details see the change notes.

Official staging repo:
  https://dist.apache.org/repos/dist/dev/mina/sshd/3.0.0-M2/
Maven staging repo:
https://repository.apache.org/content/repositories/orgapachemina-1118

Git tag:
  https://github.com/apache/mina-sshd/commits/sshd-3.0.0-M2
Change notes:
https://github.com/apache/mina-sshd/blob/sshd-3.0.0-M2/CHANGES.md


Apache MINA KEYS file:
  https://downloads.apache.org/mina/KEYS


Please review and vote!

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]

Reply via email to