http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #75 from Joern Huxhorn <joern@huxhorn.de> 2009-12-27 03:07:31 --- Concerning the dropping of support for JDK<1.5 I'd like to cite the developer of the Twitter4J API about the reasons why he will stay compatible with 1.4 for an indefinite time.

Speaking of the EOSL of JDK1.4.2, there's tree reasons Twitter4J 2.1.0 will still support JDK1.4.2 which are: 1. The EOSL is about Sun's JVM implementation. IBM WebSphere6.0 is still alive and it doesn't support Java5 or later. http://www-01.ibm.com/software/websphere/support/lifecycle/index_by_eos.html http://groups.google.com/group/twitter4j/browse_thread/thread/12d98565c78844... There are tons of active Oracle WebLogic Server 8.1 users which also don't support Java5. WLS 8.1 has been EOL'ed three months ago, but customers can get extended support with $$$.

I personally suggest them to migrate those proprietary and close-sourced application servers to open source application servers such as JBoss to save $$$.

2. Sun's JDK1.4.2 has been EOL'ed a year ago, but they're still supporting They have "Java SE for Business Release" offering and customers who don't want to migrate to the latest JDK can get support from Sun with $$$. http://java.sun.com/products/archive/eol.policy.html And once Oracle acquired Sun, Oracle could launch a lifetime support offering. -> P13 Extended Support http://www.oracle.com/corporate/pricing/technology-price-list.pdf

3. There are so many "EOL? huh? who cares?" type of people. As it is not that difficult to keep supporting JDK1.4.2 in OOTB way, I want Twitter4J to cover those people.

I think there are several projects like that which would like to stay compatible with the smallest JDK version possible. And just for the record: The official (Sun) J2SE 5.0 End of Service Life was 2009-11-03. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.