Re: Java 7

Java 6 is still used a lot in enterprise developments, I am actually more looking forward to Java 8 support due to project lambda which could have a very nice impact on readability of all these async operations we tend to chain together in GWT client applications.

On Tuesday, April 16, 2013 9:12:55 AM UTC+2, Ed wrote:

I invite you to contribute the java support 7. You can do this together with your "teammates"

Why not? 

It's all a matter of priorties, vote an issue in the issue tracker and it will get a higher priority

Wouldn't it be nice that you could latter say that you were responsibly for the jdk 7 support in gwt?

On Tue, Apr 16, 2013 at 7:28 AM, Gilberto <gilberto...@gmail.com> wrote:

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.

On Wednesday, April 3, 2013 5:09:35 AM UTC-3, Thomas Broyer wrote:

On Wednesday, April 3, 2013 8:15:03 AM UTC+2, Max Völkel wrote:

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 Java6

  runtime, please use the --use_java6 flag when deploying your app. We encourage

  you 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?

I don't know how AppEngine's Java runtime works, but my 7 and 8 JREs are very well capable of running classes compiled with -target 1.6 or earlier, and mixing classes compiled with different -target (you'd never be able to use Maven, or pretty much any third-party dependency actually, if that wasn't the case; btw GWT is compiled with -target 1.6 and is fully compatible with a JDK 7, and we haven't yet heard of anyone having issues using RPC or RequestFactory on AppEngine)

--
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-toolkit+unsubscribe@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.
 
 

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@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.