+1

Jeff


> On Jan 14, 2026, at 6:44 AM, Gary Gregory <[email protected]> wrote:
> 
> +1: I tested the source zip files and:
> 
> - ASC OK.
> - SHA512 OK.
> - Tested `mvn clean verify`.
> - With Java 17, 21, 25, 26-ea (see notes below).
> 
> - Using `java -version`:
> 
> openjdk version "17.0.17" 2025-10-21
> OpenJDK Runtime Environment Homebrew (build 17.0.17+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.17+0, mixed mode, sharing)
> 
> openjdk version "21.0.9" 2025-10-21
> OpenJDK Runtime Environment Homebrew (build 21.0.9)
> OpenJDK 64-Bit Server VM Homebrew (build 21.0.9, mixed mode, sharing)
> 
> openjdk version "25.0.1" 2025-10-21
> OpenJDK Runtime Environment Homebrew (build 25.0.1)
> OpenJDK 64-Bit Server VM Homebrew (build 25.0.1, mixed mode, sharing)
> 
> openjdk version "26-ea" 2026-03-17
> OpenJDK Runtime Environment (build 26-ea+30-2832)
> OpenJDK 64-Bit Server VM (build 26-ea+30-2832, mixed mode, sharing)
> 
> I saw this failure on the command line with 26-ea, but it didn't fail the 
> build:
> 
> [ERROR] Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 21.22 s <<< FAILURE! -- in org.apache.sshd.server.ServerTest
> [ERROR] org.apache.sshd.server.ServerTest.serverIdleTimeoutWithForce
> -- Time elapsed: 10.02 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: Waiting for too long on remote
> window size to reach zero ==> expected: <true> but was: <false>
> at 
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at 
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
> at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:214)
> at 
> org.apache.sshd.server.ServerTest.serverIdleTimeoutWithForce(ServerTest.java:432)
> at java.base/java.lang.reflect.Method.invoke(Method.java:565)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1612)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1612)
> 
> I ran the build on 26-ea twice and it happened each time.
> 
> - Using Maven 3.9.12 on macOS:
> 
> Apache Maven 3.9.12 (848fbb4bf2d427b72bdb2471c22fced7ebd9a7a1)
> Maven home: /opt/homebrew/Cellar/maven/3.9.12/libexec
> Java version: 17.0.17, vendor: Homebrew, runtime:
> /opt/homebrew/Cellar/openjdk@17/17.0.17/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "26.2", arch: "aarch64", family: "mac"
> 
> Darwin ****.local 25.2.0 Darwin Kernel Version 25.2.0: Tue Nov 18
> 21:09:56 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6041 arm64
> 
> Docker version 29.1.3, build f52814d
> 
> Gary
> 
> 
> On Tue, Jan 13, 2026 at 5:45 PM Thomas Wolf <[email protected]> wrote:
>> 
>> Hello,
>> 
>> I've staged a new candidate release for Apache Mina SSHD 2.17.0.
>> 
>> The problems of RC1 are fixed:
>> 
>> * git configs are mocked now in git-related tests
>> * the test failure on Java 25+ turned out to be a bug in our test
>>   framework
>> * Gary bumped PMD to 7.20.0 to be able to compile on Java 26-ea
>> 
>> To be able to build on Java 25, the minimum maven version required
>> is now 3.9.12. I recommend using the maven wrapper to build:
>> 
>>   ./mvnw clean verify
>> 
>> Since 2.16.0, there are some bug fixes, and an important change in
>> SftpFileSystem, which newly uses a single SSH channel for all threads.
>> Previously it used a pool of channels, but that gives trouble with SFTP
>> servers limiting the number of concurrently open channels per SSH
>> session to 1.
>> 
>> Official staging repo:
>>   https://dist.apache.org/repos/dist/dev/mina/sshd/2.17.0/
>> Maven staging repo:
>>   https://repository.apache.org/content/repositories/orgapachemina-1123
>> 
>> 
>> Git tag:
>>   https://github.com/apache/mina-sshd/commits/sshd-2.17.0
>> Change notes:
>> 
>> https://github.com/apache/mina-sshd/blob/sshd-2.17.0/docs/changes/2.17.0.md
>> 
>> 
>> Apache MINA KEYS file:
>>   https://downloads.apache.org/mina/KEYS
>> 
>> The SHA512 checksum files have been created with 'shasum -a512 -b'.
>> 
>> 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]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to