Java now has a built-in expiration date. What that's about (not obvious at first)
Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.If you may have looked at the release notes for the latest (as of this writing) JVM update (Java 1.7 update 21), you may have noticed that it refers to an "expiration date" for this version of the JVM. What's that about, you may wonder?
Comments
[Add Comment]
Thank you. Just started to find out behavior of Java message appearing.
# Posted By allexb
| 6/21/13 4:47 AM
Thank you for clearing this up. I noticed it in the u55 release notes and was worried. Many other software vendors actually *do* disable their applications automatically at a preset expiration date, and I thought Oracle was heading down the same path. It's a deplorable practice which is just one more way of hassling loyal users, and stuff like that is the reason why people in the know consider pirated/cracked software to be of higher quality than their licensed originals… glad to hear that in the case of the JRE, this was a false alarm. Oracle should really think about rewording that paragraph.
# Posted By Daniel
| 4/30/14 3:32 PM
[Add Comment]
