Some time ago I suggested that we delay the move to java 1.4 because various RDBMS vendors hadn't (and still haven't) released JDBC drivers that are compatible with the JDBC 3.0 API that is part of j2se 1.4.
A few days ago, I read through the detailed release notes for j2se 1.4 and learned that the j2se provides *binary* compatibility with JDBC drivers that don't implement the latest spec. So, while a driver creator couldn't compile their source code for an older JDBC version using Merlin, users of that driver have no problem. Of course the vendors don't say that they support the latest and greatest VMs, but that's the usual certification lag time.
I've tested current (== older) drivers using Merlin and it works fine. So, as far as I'm concerned, that eliminates any obstacles to adopting 1.4 in maxent, grok, and opennlp. Are there other outstanding problems?
Eric
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Some time ago I suggested that we delay the move to java 1.4 because various RDBMS vendors hadn't (and still haven't) released JDBC drivers that are compatible with the JDBC 3.0 API that is part of j2se 1.4.
A few days ago, I read through the detailed release notes for j2se 1.4 and learned that the j2se provides *binary* compatibility with JDBC drivers that don't implement the latest spec. So, while a driver creator couldn't compile their source code for an older JDBC version using Merlin, users of that driver have no problem. Of course the vendors don't say that they support the latest and greatest VMs, but that's the usual certification lag time.
I've tested current (== older) drivers using Merlin and it works fine. So, as far as I'm concerned, that eliminates any obstacles to adopting 1.4 in maxent, grok, and opennlp. Are there other outstanding problems?
Eric
Nope. Let's upgrade to 1.4 then.