org.apache.sshd:sshd-sftp is declared in the pom (2.16.0, the version qqq-backend-module-filesystem uses).
Why
SftpTransport imports Apache MINA SSHD directly, but the artifact was not declared: it arrived only through qqq-backend-module-filesystem. A host that also gets that module from a dependency which excludes its SSH stack resolves the module once, without SSHD. qbit-object-storage is such a dependency (it excludes sshd-sftp: "Only the S3 factory is used; do not ship the SFTP backend's SSH stack").
Seen in an application that composes both: new EdiQBitProducer().withQBitConfig(...).produce(instance) throws java.lang.NoClassDefFoundError: org/apache/sshd/common/session/SessionContext at EdiQBitProducer.produce, the line that creates the SFTP transport.
Declaring what the code imports makes the qbit independent of how a host happens to get the filesystem module. No code change.
Checks run locally
./mvnw -B verify: 270 tests, 0 failures, Checkstyle 0. dependency:tree shows sshd-sftp as a direct dependency.
## What this changes
`org.apache.sshd:sshd-sftp` is declared in the pom (2.16.0, the version `qqq-backend-module-filesystem` uses).
## Why
`SftpTransport` imports Apache MINA SSHD directly, but the artifact was not declared: it arrived only through `qqq-backend-module-filesystem`. A host that also gets that module from a dependency which excludes its SSH stack resolves the module once, without SSHD. `qbit-object-storage` is such a dependency (it excludes `sshd-sftp`: "Only the S3 factory is used; do not ship the SFTP backend's SSH stack").
Seen in an application that composes both: `new EdiQBitProducer().withQBitConfig(...).produce(instance)` throws `java.lang.NoClassDefFoundError: org/apache/sshd/common/session/SessionContext` at `EdiQBitProducer.produce`, the line that creates the SFTP transport.
Declaring what the code imports makes the qbit independent of how a host happens to get the filesystem module. No code change.
## Checks run locally
`./mvnw -B verify`: 270 tests, 0 failures, Checkstyle 0. `dependency:tree` shows `sshd-sftp` as a direct dependency.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
SftpTransport uses org.apache.sshd directly, but the artifact arrived only
through qqq-backend-module-filesystem. A host that also gets that module
from a dependency which excludes its SSH stack (qbit-object-storage does)
resolved it without SSHD, and EdiQBitProducer.produce failed with
NoClassDefFoundError: org/apache/sshd/common/session/SessionContext.
Tests: 270 run, 0 failures, Checkstyle 0.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What this changes
org.apache.sshd:sshd-sftpis declared in the pom (2.16.0, the versionqqq-backend-module-filesystemuses).Why
SftpTransportimports Apache MINA SSHD directly, but the artifact was not declared: it arrived only throughqqq-backend-module-filesystem. A host that also gets that module from a dependency which excludes its SSH stack resolves the module once, without SSHD.qbit-object-storageis such a dependency (it excludessshd-sftp: "Only the S3 factory is used; do not ship the SFTP backend's SSH stack").Seen in an application that composes both:
new EdiQBitProducer().withQBitConfig(...).produce(instance)throwsjava.lang.NoClassDefFoundError: org/apache/sshd/common/session/SessionContextatEdiQBitProducer.produce, the line that creates the SFTP transport.Declaring what the code imports makes the qbit independent of how a host happens to get the filesystem module. No code change.
Checks run locally
./mvnw -B verify: 270 tests, 0 failures, Checkstyle 0.dependency:treeshowssshd-sftpas a direct dependency.🤖 Generated with Claude Code