How to Ensure Your Code Works With Older JDKs

jOOQ is a very backwards compatible product. This doesn't only mean that we keep our own API backwards compatible as well as possible, but we also still support Java 6 in our commercial distributions. In a previous blog post, I've shown how we manage to support Java 6 while at the same time not missing … Continue reading How to Ensure Your Code Works With Older JDKs

A Subtle AutoCloseable Contract Change Between Java 7 and Java 8

A nice feature of the Java 7 try-with-resources statement and the AutoCloseable type that was introduced to work with this statement is the fact that static code analysis tools can detect resource leaks. For instance, Eclipse: When you have the above configuration and you try running the following program, you'll get three warnings: public static … Continue reading A Subtle AutoCloseable Contract Change Between Java 7 and Java 8

jOOQ and Java 7

There are more and more blog posts popping up on the internet about Java 7's bugs that crash Lucene and Solr, as well as other software. I just found this interesting post here, from a Lucene developer: http://blog.thetaphi.de/2011/07/real-story-behind-java-7-ga-bugs.html I wonder what the implications of using Java 7 will be for jOOQ users. So far, no … Continue reading jOOQ and Java 7