[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[orbit-dev] Anybody want JSch-0.1.38?
|
Dear
Orbiters,
to ask on the Orbit
mailing list if anybody is interested in getting
JSch-0.1.38
(currently, we're maintaing JSch-0.1.37 as part of
the Platform, it's
used for Team/CVS SSH and RSE SSH):
Now 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 in DSDP-TM, 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?
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
