Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Java Programming Oracle Upgrades

Java 6 EOL'd By Oracle 115

Tmack writes "Not completely unexpected, Java6 has reached EOL. This tidbit shows up in Oracle's Java6 FAQ page, recommending everyone update to Java7: 'Oracle no longer posts updates of Java SE 6 to its public download sites. All Java 6 releases up to and including 6u45 have been moved to the Java Archive on the Oracle Technology Network, where they will remain available but not receive further updates. Oracle recommends that users migrate to Java 7 in order to continue receiving public updates and security enhancements.' Apple just pushed its update 16 which is Java6u51, likely to be one of their last Java6 updates."
This discussion has been archived. No new comments can be posted.

Java 6 EOL'd By Oracle

Comments Filter:
  • by Sique (173459) on Thursday June 20, 2013 @03:58PM (#44064765) Homepage
    I still have sometimes to use tools that were developed for Java 1.3.1 and barely run with Java 1.4.2.
  • Re:Hating Oracle (Score:5, Informative)

    by devman (1163205) on Thursday June 20, 2013 @04:40PM (#44065121)
    Since JDK6, Oracle Java is based on OpenJDK. Unless your using one of the specific features oracle tweaks or adds you should be fine.
  • by Anonymous Brave Guy (457657) on Thursday June 20, 2013 @06:35PM (#44065949)

    Java 6 will still run.

    Actually, no, sometimes it won't. I have personally spent most of today fielding support problems because the "improvements" in Java applet security in 6u51 (mainly for Apple users) and 7u25 have meant precisely that systems that were working just fine yesterday are not working today.

    It's like people think "Set build option X and it'll work again" or "You need to sign it with magical certification Y at time Z now" is a viable response. In reality, many Java applets are used other than as part of a maintained public web site, and once deployed maybe they can't easily be updated. They might be part of a secure intranet where any changes need expensive regulatory approvals to be redone. They might be part of a user interface embedded in network-accessible hardware. It might just be a useful demonstration on an academic's web site that they wrote ten years ago but don't maintain. In the last 48 hours, these and many other cases all broke.

  • by Chris Mattern (191822) on Thursday June 20, 2013 @07:26PM (#44066245)

    The problem isn't that Java 7 isn't production ready. The problem is the large amount of production that isn't Java 7 ready.

  • by Anonymous Coward on Thursday June 20, 2013 @09:45PM (#44067029)
    I have never had an issue with minor point released for Java. Of course I am not a dipshit and actually try and use undocumented parts or rely on a version specific bug. You would have to be a special kind of asswipe to do crap like that. Oh, wait a sec, that is the entire Java "enterprise" community. Asshats one and all

Business will be either better or worse. -- Calvin Coolidge