Now, when the new, faster, release schedule was announced, Oracle announced that every 3 years, there would be an LTS (Long Term Support) version of Java. That said, there are plenty of advantages for upgrading to JDK 11+, better performance being one of them. The good news is that there are still public (and free) updates coming from the OpenJDK 8 maintenance project. The same arguments could be made for JDK 8 as well, on a slightly pushed out time-line. Now, if you’re not running a JDK 7 with the latest patches (sanity check – was the JDK at least built this year?), you may not only be missing out on bug fixes, but you may also be missing out on security patches! Also, this particular upgrade (7->8) should be relatively painless – in most cases it will be a drop in replacement. If you aren’t buying support and have someone provide you with (security) patches, you might want to accelerate the effort. JDK 7 is dying and support is being dropped left and right. In other words, if you’re still running your software on JDK 7, you may want to at least begin upgrading to 8. You are now five (5!) years behind on critical security patches. If you got your JDKs from Oracle, without a support contract chances are that the latest version of JDK 7 you got was built in 2015. Oracle’s Premier Support ended in July 2019, and even the Extended Support ends 2022. Publicly available updates and fixes ceased in April 2015. Which is funny, in a way, since everything you’ll be running could be affected. However, not everyone is keeping their JDKs/JVMs up-to-date. GitHub may even warn you if you’re running with a version that has known security implications. For example, if you’ve written something with a dependency on Tomcat, you are pretty likely to keep your dependencies up-to-date. Typically most companies will require that you keep your dependencies up-to-date. Docker Hub, and you may not know exactly what you’re getting. This is especially important, since you might be consuming your JDK from a container provided by a third party, e.g. You’ll need to get those directly from the vendor.Īfter trying to figure out what’s what, I thought I’d simply write a blog post on the various JDKs available out there. They can have different support lengths for specific versions, and whereas you can sometimes find a vendor providing extended support for a version that has been officially end-of-lifed at Oracle, you may not find builds with the latest fixes in them publicly available. There are quite a few different vendors out there, providing support and taking responsibility for the binaries they produce. Eventually you’ll need to decide on which JDK/JRE to deploy your software on in production. Many of you are using a variety of other languages that target the JVM, such as Scala, Kotlin, Clojure, Groovy, (J)Ruby etc. Since you’re reading this blog, chances are that you’re writing software which will eventually run on a JVM. Once upon a time he co-founded Appeal, the company creating the JRockit JVM. Marcus is the project lead for the Open JDK JMC project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |