That would be a problem... A quick google[1] suggests people were asking about it last July, but that it was dependent on Eclipse's JDT having support (which it now has), so it looks like it is just waiting for GWT.
Splitting the code between server + client has been needed for a while, but I doubt it would be feasible to do to allow compiling them against different versions of the JDK. The hard bit of doing this would be determining what to do with all the code common to both (protobufs, models etc.) [1]: https://groups.google.com/forum/#!topic/google-web-toolkit/dM8D9imIvAI/discussion On 31 January 2012 22:03, Thomas Broyer <[email protected]> wrote: > Just a note: GWT doesn't support Java 7; but server-side code could use it > if needed. > Le 31 janv. 2012 22:57, "Ali Lown" <[email protected]> a écrit : > >> Any plans on moving to Java 1.7 support instead? >> >> I just tested with openjdk-7-jdk-amd64 (on Debian), and found that the >> ProtoBuf's failed to compile citing errors such as: >> compile-proto: >> [javac] Compiling 11 source files to /wave/build/proto >> [javac] >> /wave/proto_src/org/waveprotocol/box/common/comms/WaveClientRpc.java:971: >> warning: [static] static method should be qualified by type name, >> Builder, instead of by an expression >> [javac] super.addAll(values, result.waveletIdPrefix_); >> [javac] ^ >> [javac] >> /wave/proto_src/org/waveprotocol/box/common/comms/WaveClientRpc.java:1022: >> warning: [static] static method should be qualified by type name, >> Builder, instead of by an expression >> [javac] super.addAll(values, result.knownWavelet_); >> [javac] ^ >> [javac] >> /wave/proto_src/org/waveprotocol/box/common/comms/WaveClientRpc.java:1895: >> warning: [static] static method should be qualified by type name, >> Builder, instead of by an expression >> [javac] super.addAll(values, result.contributor_); >> [javac] ^ >> ----Snip lots of these---- >> >> I ask this because of Java 1.7's support for TLS 1.2 which I think may >> help with the SSL issues with ICS/OpenSSL. >> >> Ali >>
