I think the only effect to those 100's of products is that they can't use the EmbeddedJSP plugin, which needs a feature that is only supplied with Java 6+. Am I missing something other implication? (*Chris*)
On Sun, Aug 23, 2009 at 9:30 PM, Martin Cooper <mart...@apache.org> wrote: > On Sun, Aug 23, 2009 at 8:48 PM, Kent R. Spillner<sl4...@zerosphere.org> > wrote: > > Howdy- > > > > > >> I'll go see if google can tell me about the lifespan of > >> Java 5. > > > > > > About 10 weeks. :) > > That's Sun's support expiration, which has very little, if anything, > to do with the lifespan of Java 5. > > Large enterprises aren't going to switch to a new Java version just > because Sun stops supporting the one they're using. The company I work > for, for example, has hundreds of products (no, I'm not kidding) built > on Java 5. Switching to Java 6 or 7 will be a very large effort for > us, and not one we'll undertake lightly. And new products will still > be based on Java 5 for now, since that's what our platform is built on > today. > > There were large incentives, in terms of new language features, that > encouraged people to move to Java 5, and even that migration took > several years. Java 6 didn't provide much in the way of significant > incentives, so many, many organisations simply didn't move. Many of > them will hold out and skip to Java 7, meaning that the lifespan of > Java 5 will be that much longer. > > -- > Martin Cooper > > > > http://java.sun.com/products/archive/eol.policy.html > > > > Best, > > Kent > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > > For additional commands, e-mail: dev-h...@struts.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
