Page 2 of 2

Posted: Fri 19 Apr 2013, 07:40
by jpeps
Monsie wrote:
Why is this? Does this mean: this patch is a beta release --soon to be replaced by a stable build? Or, is Oracle really referring to the SDK rather than the JRE?

Monsie
"It's the date by which Java will consider itself out of date"

You probably didn't realize that java could do that, right?

http://stackoverflow.com/questions/1606 ... ation-date

Java security

Posted: Sat 20 Apr 2013, 06:35
by Monsie
jpeps wrote:
Monsie wrote:
Why is this? Does this mean: this patch is a beta release --soon to be replaced by a stable build? Or, is Oracle really referring to the SDK rather than the JRE?

Monsie
"It's the date by which Java will consider itself out of date"

You probably didn't realize that java could do that, right?

http://stackoverflow.com/questions/1606 ... ation-date
Thanks, jpeps

You are correct, I did not realize that a so called expiration date was set in each release. I may be wrong here, but I am thinking that this is policy that Oracle implemented and not Sun. My take is that it is really more useful to the developer/maintainer than Joe Consumer (pun intended) because it will likely fit with the (Oracle) schedule of maintenance releases... and besides, Java is configured to check for updates monthly anyway.

Monsie

Posted: Thu 20 Jun 2013, 10:46
by Semme

Posted: Wed 11 Sep 2013, 12:42
by Semme

Posted: Wed 16 Oct 2013, 10:35
by Semme

Posted: Tue 14 Jan 2014, 20:40
by Semme

Posted: Thu 20 Mar 2014, 12:38
by Semme

Posted: Thu 17 Apr 2014, 12:16
by Semme
Both 7 & 8, two days ago..