Ok,
I have removed JSch-0.1.37 from the HEAD builds:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=338433
I also fixed the PSF and JSch readme.txt
I did not remove earlier JSch versions (including 0.1.28 and 0.1.31) from the com.jcraft.jsch.xml in the ip_logs directory.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: Saturday, February 26, 2011 12:29 AM
To: Orbit Developer discussion
Subject: Re: [orbit-dev] Last chance for M6 coming up: 3/4
> Does this make the older version a candidate for removal?
Yes, I think so. If no one using the 0.1.37 version, or likely no one is using it, especially for years, we can remove it from active builds. If it turns out someone was depending
on it being there for Indigo for some reason, we can add it back in (and, in the mean time, they could get from previous R-build, or previous S-build in this case).
Thanks,
From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
To: Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Date: 02/25/2011 11:29 AM
Subject: Re: [orbit-dev] Last chance for M6 coming up: 3/4
Sent by: orbit-dev-bounces@xxxxxxxxxxx
Regarding cleanup:
com.jcraft.jsch_0.1.37 was last used in Eclipse 3.4
The newer versions (0.1.41 is “current” since Eclipse 3.5; 0.1.44 is “experimental”) are just bugfix versions, I’m not aware of any regression or compatibility problem.
Does this make the older version a candidate for removal?
Regarding the other bundles I care for (Apache ORO and Commons Net) I’d vote for keeping the old ones around for now since they support Java 1.4 and below whereas the newer ones
all require Java 5.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From:
orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: Thursday, February 24, 2011 7:15 PM
To: Orbit Developer discussion
Subject: [orbit-dev] Last chance for M6 coming up: 3/4
If I am looking at the calendar right this time, M6 +0 is in two weeks, on 3/11. Therefore, I propose we promote our Orbit contributions to an S-build for Indigo participants to use on Friday,
3/4.
Let me know if this date is a problem, or if you have a better suggestion.
And, being M6, this is the last chance we have to remove any "old" stuff, according to our recently revised retention policies [1] ... so please check. If you have something that could be removed from current builds, now is the time to do it. Otherwise it stays,
no matter how old, until July. Feel free to ask here on this list, if questions. (And, I won't mention the one person who removed one thing prematurely ... but, I appreciate the aggressive cleanup DJ. :)
Thanks everyone,
[1] http://wiki.eclipse.org/Orbit/Promotion%2C_Release%2C_and_Retention_Policies#Bundle_Retention_in_active_builds
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
