Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #191263 +++ A (small but important) number of bugs have been identified in JSch 0.1.31 which is shipping with Eclipse 3.3 - including bug 191263 (platform-cvs), bug 204705 (dsdp-tm), bug 208912 (dsdp-tm), bug 220853 (dsdp-tm) JSch should be upgraded to version 0.1.37 for Ganymede. Corresponding CQ has been approved already as per http://dev.eclipse.org/ipzilla/show_bug.cgi?id=2014 So JSch-0.1.37 should be added to Orbit and included in Platform builds.
(In reply to comment #0) > So JSch-0.1.37 should be added to Orbit and included in Platform builds. As far as I have recognized, to push it into Eclipse Platform, we need the approval by EMO(part of which would involve the creation of the required 'about.html' file). I don't know if it is in the process or not. If not, I don't know how to start the process(request for the approval). For previous Eclipse Platforms, Michael had worked on it. Any suggestions are welcome.
I have obtained permission for checking JSch-0.1.37 into Orbit as per http://dev.eclipse.org/ipzilla/show_bug.cgi?id=2158 and have committed it to the Orbit Repository, /cvsroot/tools, org.eclipse.orbit/com.jcraft.jsch, branch=v0_1_37 I took and adapted the about.html as well as parts of the Manifest meta-info from JSch-0.1.31, I'm now waiting for the Orbit Build to complete such that I can download and test the bundle, and the Eclipse Platform PMC to approve re-use in the Platform as per https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2014#c22 For Orbit build Status you can follow this if you want: http://build.eclipse.org:9777/cruisecontrol/buildresults/orbit-I
JSch-0.1.37 is built in Orbit and available from http://download.eclipse.org/tools/orbit/committers/drops/I20080305144804/ Eclipse Platform PMC has allowed inclusion in Platform as per https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2014#c24 Kim or Michael can you please update the Platform CVS Feature to include the new JSch as soon as a stable Orbit build is declared.
An Orbit I-build which includes JSch-0.1.37 has been promoted to downloads: http://download.eclipse.org/tools/orbit/downloads/drops/I20080307200012/ This I-build will remain available for long. Please update Platform Features to use JSch from this build, and release for next Platform I-build.
Yes, I will update to a newer orbit build this week. I'm just waiting for all the issues with the I-build to be sorted out first.
released for I20080323-2000.
For everybody's info, JSch-0.1.38 has been released: http://sourceforge.net/mailarchive/forum.php?thread_name=200804221521.AAA16510%40jcraft.com&forum_name=jsch-users Changes since version 0.1.37: 1) bugfix: NPE should not be thrown at unexpeced session drop. FIXED. 2) bugfix: AIOOBE at Session#connect(). FIXED. 3) bugfix: Even if 'true' is given for Channel#setOutputStream( OutputStream out, boolean dontclose) as the second paramter, 'out' will be closed. FIXED. 4) change: 'examples/Sftp.java' has been modified to demonstrate ChannelSftp#realpath(String path) 5) change: setEnv(Hashtable env) for exec and shell channels have been marked as @deprecated 6) feature: setEnv(String name, String value) has been added to exec and shell channels. 7) feature: setEnv(byte[] name, byte[] value) has been added to exec and shell channels. 8) feature: ChannelSftp#realpath(String path) has been added. 9) feature: ChannelExec#setCommand(byte[] command) has been added. 10) feature: com.jcraft.jsch.ChannelSftp.LsEntry has implemented java.lang.Comparable 11) feature: Session#getServerAliveInterval(), Session#getServerAliveCountMaX() have been added. For us, fixes (1) and (7) are interesting though not a "must have" for Ganymede. Is anybody else interested such that I should go and file an IPZilla / Orbit request? Is it even realistic to get 0.1.38 in for Ganymede? My personal take is that I'd like to go and try getting it into Orbit, then we can still decide whether the Platform's going to adopt it out of Orbit or not. Sounds reasonable?
Martin, I think it would be advisable to ask this question on the orbit mailing list for a wider audience. I haven't heard anything about us adopting the newer version but others will know more :-)
