Also, GWT added support for Java 5 when Java 1.4 reached EOL, and Java 6 was already released, and GWT does not officially support Java 6 (that's going to change, and a few features are already there, such as @Override on implementations of interface methods, and String#isEmpty); let's hope it'll be faster for Java 7, but don't be too impatient IMO.
Note: As of GWT 1.5, GWT compiles the Java language syntax that is compatible with J2SE 1.5 or earlier. Versions of GWT prior to GWT 1.5 are limited to Java 1.4 source compatibility. For example, GWT 2.0 supports generics, whereas GWT 1.4 does not.
Hi,
sorry for gravedigging, but the title of this thread seems suitable.
Since Java 6 reaches its End-Of-Life cycle at the beginning of next year, does the GWT team has concrete plans to support Java 7?
See: http://www.oracle.com/technetwork/java/eol-135779.html
Cheers,
Ben
Sorry for resurrecting a slightly old thread.JDK 1.6 is EOL end of this month, so I am thinking of migrating my GWT project to JDK7I am using GWT 2.5, and wondering if many people are using JDK7 in their GWT projects. Is it okay to do so and if so, what are the gotchas?
Hi,Sorry for resurrecting a slightly old thread.JDK 1.6 is EOL end of this month, so I am thinking of migrating my GWT project to JDK7I am using GWT 2.5, and wondering if many people are using JDK7 in their GWT projects. Is it okay to do so and if so, what are the gotchas?
How well does this play together with AppEngine 1.7.7? From their release notes: "The Java runtime now defaults to Java7. If you still need to use the Java6runtime, please use the --use_java6 flag when deploying your app. We encourageyou to move to Java7 as soon as possible."It sounds I should compile for a 1.7 target. So I should *not* set maven.compiler.source to 1.6, right?
--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/dM8D9imIvAI/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsub...@googlegroups.com.
It's just my opinion, but in my mind making the JDK compliance to 1.6 and call that "fully compatible with JDK 7" is not... well... what I was expecting (at least).
I understand that tweaking the compiler to actually and truly support Java 7 is not easy and demand time. But Java 7 is around for ... uh... years? (since July - 2011 according to Wikipedia). I understand that GWT is now handled by a committee, since last year. And still, there's no public roadmap of when we are going to have the real Java 7 support (and I'm not even talking about Java 8). So, eh, am I wrong on asking such things? Should I recommend other frameworks to my teammates for new projects or still wait for news from GWT?
I understand we have to wait till you guys commit the code to Gerrit/GitHub, to organize the project, to mavenize it, to deal with contributors, Google itself and so on. But till when?
Sorry for my impatience, but at this stage I don't really feel comfortable with the situation. Maybe it's only me.