slachiewicz commented on issue #680: URL: https://github.com/apache/maven-wagon/issues/680#issuecomment-5225540632
Still current, and the case is stronger now than in 2021. `wagon-ssh` is unchanged on this front: ```xml <groupId>com.jcraft</groupId> <artifactId>jsch</artifactId> <version>0.1.55</version> <!-- last released 2018 --> ... <artifactId>jsch.agentproxy.connector-factory</artifactId> <version>0.0.9</version> ``` The provider page says it is deprecated and will be removed in 4.0.0, and that could be read as a decision against doing anything here. It should not be, because 4.0.0 does not exist: - the last release is 3.5.3, and this branch is 3.5.4-SNAPSHOT; - `master` is 4.0.0-M1-SNAPSHOT and has never been tagged; - both a Maven 3.9.16 distribution and a build of Maven 4.0.0-SNAPSHOT bundle `wagon-*` at **3.5.3**. So the line that ships is 3.x, it is expected to stay for the time being, and it carries an SSH stack whose upstream stopped releasing eight years ago. That is a maintenance risk independent of whatever 4.0.0 eventually does. Worth considering together with #503, which reports SSH agent authentication broken since 2.10 and sits on `jsch.agentproxy` 0.0.9 — the same unmaintained corner. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
