Matthias Wiedemann

@norrisjeremy ok for me. Original Jsch code has been there for a while. No rush on the formatting. (or even variable naming :grin:)

Yes I am aware of this. I set up Sonarcloud analysis for this repo. Compare here https://sonarcloud.io/dashboard?id=mwiede_jsch On Fri, Jul 17, 2020, 16:38 antoxar wrote: > [image: image] > >...

Correct. I deactivated it as it did not work on pr builds.

Sent current code analysis to Sonarcloud. https://sonarcloud.io/project/overview?id=mwiede_jsch Java Source and Coverage included

in general, I would be open to support such a flag, the only thing is, that we should keep the API of original Jsch, so that exchanging the library does...

yes I have also researched about other forks and I was trying https://techgaun.github.io/active-forks/index.html to get activity stats is/jsch does not seems active and does not release its code. But maybe...

I started a module based on jsch. Please have a look at it https://github.com/mwiede/docker-java/blob/master/docker-java-transport-ssh/Readme.md Some problems in direct attached stream and integration suite still exist. On Tue, Jun 2, 2020,...

The SSH transport channel provides a socket to call the Docker API on the host, not the Docker CLI. I described this setup on https://github.com/mwiede/docker-java/blob/master/docker-java-transport-ssh/Readme.md On Sat, Jun 20, 2020,...

Thanks @bsideup this should make it possible to publish ssh transport module of #1440 separate from this project.

FYI I have released a module supporting ssh protocol at https://github.com/mwiede/docker-java-transport-jsch