Migrate to JDK 21 unix sockets - #9597
Conversation
4ae03b4 to
a682108
Compare
matthiasblaesing
left a comment
There was a problem hiding this comment.
Upload of files in PHP projects still works without asking for passwords, so jsch works and agent integration is also active.
A terminal connection to a remote system was possible, so I suspect dlight is also happy.
The change to docker is breaking the module (suggestion for fix is in the inline comment).
If I understand this correctly: norrisjeremy/jsch@1cd3980 the jzlib libraries were integrated into jsch. We can drop the dependency of com.jcraft.jsch on com.jcraft.jzlib. ide/c.jcraft.jzlib is then a candatidate for removal.
a682108 to
ab99234
Compare
|
removed jzlib and updated occurrences in
|
matthiasblaesing
left a comment
There was a problem hiding this comment.
Looks sane to me. Thank you.
|
wanted to update the remote shell connection dialog a bit since its size is currently too small to fit the auth method dropdown but had no time. Will try doing that in a followup since its independent anyway. will rebase and merge |
- jsch lib update - and JDK 21 baseline allows kohlschutter-junixsocket removal - migrated docker.api to JDK api - fix BundleException by setting Bundle-ManifestVersion=2 - removed jzlib wrapper since it is now shipped with jsch - adjust module-auto-deps and other configs to the new situation Co-authored-by: =?UTF-8?q?Matthias=20Bl=C3=A4sing?= <mblaesing@doppel-helix.eu>
ab99234 to
49591d6
Compare
The recent felix / jgit cleanups should allow us to update jsch which was a blocker for removal of
ide/libs.c.kohlschutter.junixsocket. The secondary blocker was lack of lower bound JDK 21.This is also in context of #9594 (comment) which reminded me on this.
com.jcraft.jschis used innot well tested - testing help appreciated.