From: Stuart D. Gathman <stuart@bm...> - 2006-07-07 18:45:58
On Fri, 7 Jul 2006 jython-dev-request@... wrote:
> > Can I ask the reason for wanting to stay compatible with JDK 1.2?
> I guess the reason to stay compatible with JDK 1.2 is to maximize the
> potential environments where Jython can be used. For example, the
> JDK that comes on some phones is limited to JDK 1.2 and many (most?)
> application servers are currently limited to (I believe) JDK 1.3. I
> think Jython should be careful with increasing the minimum version of
> the JDK, to avoid closing potential users out.
I, for one, am very appreciative of being able to run Jython 2.1 on JDK 1.1.
> That being said, we also have to balance that with the limited
> resources (mainly number of active developers on Jython). That is one
> of the reasons we are changing the minimum JDK from 1.1 to 1.2 (that
> and collections integration). While I really want to be more
> aggressive with the minimum JDK (I'd love to use java.nio.* from JDK
> 1.4 and the much better threading support from JDK 1.5) I don't think
> it is time for that yet.
Yes, we have servers that are stuck at an OS level for 5 years or more.
The latest JDK often requires an OS upgrade, which is not always feasible
for a 24/7 server. Certainly, on my desktop I have the latest Fedora Core
and JDK, but we have servers running RedHat 7.3 (with fedoralegacy.org security
patches) and AIX 4.3.
So the current 1.2 policy is very reasonable. (I understand about letting
JDK 1.1 go - collections are too important.)
Stuart D. Gathman <stuart@...>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.