| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | John Lister <john(dot)lister-ps(at)kickstone(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Java 1.4 |
| Date: | 2012-01-24 17:52:41 |
| Message-ID: | alpine.BSO.2.00.1201231420110.30215@leary.csoft.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Sat, 21 Jan 2012, John Lister wrote:
> I noted from the recent NIO thread that support for Java 1.4 was
> checked. I know from previous discussion that this has been brought up,
> but was wondering if there was a reason for still supporting 1.4? I
> therefore wondered if it is still worth while supporting something
> released nearly 10 years ago and nearly 8 years since its last update
> and not freeze a version for that release (except maybe security related
> updates). Similarly would it be wise to freeze the jdbc 2 & 3 updates as
> well since they require Java 1.4 and concentrate on jdbc 4 support and
> maybe Java 1.5 (or even 1.6) and the additional features?
>
I am all for dropping support for 1.4. If people are having a hard time
finding a 1.4 JDK to build/test with now, that's only going to be a bigger
problem down the road. I still need a 1.2 JDK to make back branch
releases for 8.2 and 8.3 and that's a real pain.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2012-01-24 17:53:37 | Re: Java 1.4 |
| Previous Message | Dave Cramer | 2012-01-24 14:51:39 | Re: Java 1.4 |