Java 7 Reaches End of Life

| by Abraham Marín Pérez Follow 9 Followers on May 05, 2015. Estimated reading time: 2 minutes |

Oracle ceased public availability of security fixes and upgrades for Java 7 as of April 2015, urging users to migrate to Java 8 or to purchase commercial long-term support for Java 7. Further public updates may be available by other vendors.

The planned EOL was originally announced in March 2014. While this is not expected to affect ordinary users (Oracle created an automatic self-update to Java 8 in January 2015), Java developers and users of advanced applications may experience some issues. Many tools and libraries still rely on features that were marked as deprecated in Java 7 and entirely removed in Java 8, making them incompatible with the newer version; these tools will have to be modified before users can upgrade their version of Java.

The fact that Oracle won’t publish any more updates doesn’t mean that Java 7 will stop working altogether, but it does mean that patches will not be provided for any new vulnerability that might come up, thus leaving users at risk. This implies that users of tools that are currently incompatible with Java 8 will have to choose between keeping Java 7 and accepting the potential exposure, purchasing commercial long-term support or migrating to a different tool. This last point is putting pressure on tool creators, particularly those responsible for open-source projects, since they need to combine their day-to-day duties with the work needed to migrate to the latest Java. This is the case for instance with Ryan Heaton, Principal Engineer at FamilySearch and creator of Enunciate, a widely used documentation engine for Java that doesn’t currently work with Java 8.

I think the EOL for Java 7 came up really fast. I wish they had waited a bit longer, but I also understand that it’s expensive to maintain older products and APIs. If I’m really honest with myself, I probably would have felt that the EOL came up fast no matter when Oracle decided to schedule it. Admittedly, it gives me extra motivation to get my projects updated.

On the other hand, it seems unusual that there isn’t more than one option for migration. Shouldn’t Java 9 be available before Java 7 is EOL?

Alternatives to Oracle JVM

While Oracle's is the most popular, it is not the only JVM available. Different vendors and user groups have created dozens of JVM implementations, both open source and proprietary, and offering different levels of support. Some of them, like Azul Systems, offer two different JVMs with commercial support that includes updates not only for Java 7, but even for Java 6.


Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Lock-in to Java 7 is doubly bad by Dean Schulze

Tool vendors who are preventing developers from moving to Java 8 are committing multiple offenses. They open their users / customers up to security vulnerabilities as this article mentions. They are also preventing their users from adopting the highly desirable improvements made to Java 8 like lambdas.

Tool makers: Next time avoid using the private APIs that you are not supposed to be using so you will not be faced with big re-writes when the next version of Java is released.

Now get off of your arses and please make your tools compatible with Java 8.

Re: Lock-in to Java 7 is doubly bad by Chris Kelly

@Dean Schulze

Drinking too much coffee in the morning perhaps :D

Re: Lock-in to Java 7 is doubly bad by Abraham Marin-Perez

To be completely fair, some of the tools are old enough so as to have been created with whatever was available at the time (even if that's now deprecated). That's the case of Enunciate, the tool mentioned in the article: it doesn't work with Java 8 because it relies on ATP, but Enunciate was created before Java 6 was available, which means ATP was the only option.

The future of contributions to OpenJDK 7 by Abraham Marin-Perez

Judging by conversations happening these days in the OpenJDK7 Dev email list, it seems Java 7 might still get some level of support, just not from Oracle.

Re: Lock-in to Java 7 is doubly bad by Allan Ford

Have just recently started with Java 7 ..
was prev. using Java 1.6 ..

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

5 Discuss