On 12-04-16 08:59 PM, Arne Vajh?j wrote:
On 4/16/2012 6:36 PM, Richard Maher wrote:
"Lew"<lewbloch@gmail.com> wrote in message
news:16106106.159.1334611367345.JavaMail.geo-discussion-forums@pbcsi9...
Richard Maher wrote:
My issue maybe as simple as jumping the gun on Java7. I thought it has
been
mainstream for yonks but it looks like it's still beta; is that
correct?
No. Java 7 was released on 2011-07-07.
Sounds more like it. I came across
http://www.java.com/en/download/faq/java7.xml and seeing Google
pushing 6.31
I got confused.
Java 6 is still being updated.
And there are probably still more on Java 6 than on Java 7.
Java 7 is the first release of Java that I've had trepidation about
moving onto. A number of Java applications I use failed silently on 7:
no exceptions, just some commanded operation or the other wouldn't
happen. As soon as I pointed them back at 6 the apps worked perfectly OK.
I see from release notes that a number of these apps have fixed
*something* since last summer that lets them work with Java 7. On the
other hand, when I see an application release note that's worded like
"this now works with Java 7", and the timing of that note is shortly
after a Java 7 update, was it the app that got fixed, or Java? Short of
asking each and every one of these application teams what it was that
got fixed, which I don't have the time for, I'm assuming that it was Java.
optimization bug (Lucene bug) that were fixed in an update.
And WAS 8.5 is just recently out in beta.
JBoss 7 has supported SE 7 for at least a half year.
It will take 2-3 years before SE 6 will be "old" in the EE world.