Decrease in support of JRE 1.3

We provide a popular open source Java FTP library called edtFTPj .

We would like to refuse support for JRE 1.3 - this will clear the code base and also allow us to more easily use the functions of JRE 1.4 (without resorting to reflection, etc.). JRE 1.3 for over 7 years!

Does anyone still use JRE 1.3? Does anyone know any polls that give an idea of โ€‹โ€‹what percentage of users still use 1.3?

+3
java
source share
7 answers

Sun allows you to buy support packages for discounted software such as JRE 1.4. For banks and some other organizations, paying $ 100,000 a year to support an outdated product is cheaper than updating. I would suggest only offering paid support for JRE 1.3. If someone needs support for this, they can pay for a hefty support package. Then you will postpone your current code base 1.3, and if a client with a support contract requires fixing bugs, then you can fix version 1.3 for them, which most likely means simply selective application of the patch from a newer version.

+6
source share

Even in October 2008, JDK 1.4 completed its support. I think you're safe.

But do not take it from me. The people you really need to ask are your customers. You may be able to try out your download page and help get feedback. If no one asks after three months, leave it.

+4
source share

Why not run your program with which version of Java it runs. This will give you an idea of โ€‹โ€‹your user base.

I highly recommend abandoning Java 1.3 support, and instead of performing a small upgrade to Java 1.4, why not use Java 1.6? Since then, there have been significant improvements. You really are missing out.

+3
source share

End of life is a normal part of the software life cycle.

The real question you should ask / answer is whether you have an urgent business need to add features to the "old" versions. If not, you can continue to offer it to customers who need it - but encourage everyone else to take the last and largest, which requires 1.4 (or 1.5 / 1.6).

+2
source share

It is difficult to give figures for what companies use domestically. There are values โ€‹โ€‹for installing the browser plugin, but Sun's numbers are confidential.

1.3 support was stopped some time ago (Solaris 8 vintage support stretched a bit). 1.4 has completed its end of service, but is likely to be supported in Java for Business for yonks. IIRC, if you try to download 1.4 from the archives on sun.com, you will be asked to enter some information, such as an email address. 1.5 is more than half life (but it's still pretty common on Macs).

Itโ€™s not so difficult to use 1.4 functions. You just need to load one class through reflection (or just put it differently) and then implement 1.4 and 1.3 realistic abstraction over new functions.

+1
source share

Why not just critical fixes for 1.3 and 1.4, if someone really requests them and makes all new versions on 1.5 - the current oldest version supported by Sun?

+1
source share

I developed with jdk 1.4 for a long time, while jdk 6.0 was missing. We could not update (this clients, blablabah servers). At some point, we just updated, not talking too much about it. Clients are updated without annoyance, "this update will fix many security holes, many bug fixes, improve performance :-)."

At the moment I'm trying to make my code compatible with jdk 1.5, I have no concern for people working under 1.4 and below. At some point, they will realize that it is in their interest to โ€œtryโ€ to upgrade.

+1
source share

All Articles