my dog learned polymorphism
The moose likes Features new in Java 8 and the fly likes Migration Strategy from Java 7. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Features new in Java 8
Bookmark "Migration Strategy from Java 7." Watch "Migration Strategy from Java 7." New topic

Migration Strategy from Java 7.

Douglas Rowe

Joined: Dec 09, 2003
Posts: 12
What do you expect to be the most problematic points in migrating a code base from Java 7? How long do you suggest waiting after a new release to begin?

Whenever you find yourself on the side of the majority, it is time to pause and reflect. Mark Twain
Campbell Ritchie

Joined: Oct 13, 2005
Posts: 46349
Why do you expect problems at all? It will be learning the new features which you will find taxing. When I went to Devoxx in June, people were advising us to move onto Java8 as soon as possible.
Ulf Dittmer

Joined: Mar 22, 2005
Posts: 42965
In a business setting it wouldn't be appropriate to migrate to a new version of anything simply because it exists. The expected benefits need to be weighed against the drawbacks. Even if no code changes are required (which is entirely possible when upgrading to a newer Java version), there's an overhead in sys admin time, possible system downtime, testing effort etc. Developers wanting to use the new features aren't the only stakeholders involved.
Richard Reese
Ranch Hand

Joined: Jul 13, 2011
Posts: 84


Learning the new features of Java can be challenging, but most of the difficulties are probably organizational. I agree with Ulf that you need to weigh the cost versus the benefits. When migrating from Java 7, I suspect one problem you may encounter is the temptation to rewrite existing code to take advantage of the new features. Using the latest and greatest approach can be appealing but ultimately it is a business decision.

Richard Reese
Java 8 New Features: A Practical Heads-Up Guide
Sean Corfield
Ranch Hand

Joined: Feb 09, 2011
Posts: 282

One area that might cause problems is tooling. For example, we rely heavily on New Relic for monitoring and they do not have production-level support for Java 8 yet. Their 3.8.0 and 3.9.0 libraries have only "experimental" support for Java 8 and only for Java 7 compatible code running on the Java 8 JVM and they are saying not to use Java 8 in production with New Relic yet.
I agree. Here's the link:
subject: Migration Strategy from Java 7.
It's not a secret anymore!