Those are warnings, and should not break the build (unless maybe you use
-strict).
Ideally the GWT compiler should be run with java 8, but you can compile (JavaC)
your classes with java 7 and deploy gwt-servlet to a 1.7 JVM.
--
You received this message because you are subscribed
Can a GWT 2.8 project still be run with Java 7? I have it working with
beta1, but not any of the release candidates or the final release?
When I do try to use anything beyond GWT beta1, I receive a series of
errors similar to the below statement
[WARN] Ignoring unresolvable annotation type
crossed they get round to Java 8 sooner rather than later!
On Thursday, 10 March 2016 16:06:47 UTC, Paul Mazzuca wrote:
>
> Thanks as alway for the prompt response. I went ahead and reverted to
> Java 7 (while still using GWT 2.8) as the quick solution, with Google
> Guava for some m
Thanks as alway for the prompt response. I went ahead and reverted to Java
7 (while still using GWT 2.8) as the quick solution, with Google Guava for
some more advanced Java 8 like APIs. After some cursory research, I
believe the GAE sandbox will be supporting Java 8 at some point this year,
so
in the client code (resolved from local Maven repo).
The cleaner solution IMO is to use separate JDKs (or proper cross-compilation,
with bootclasspath et al); either with toolchains or separate build phases.
Retrolambda would need some testing in a Java 7 environment to confirm the
transformation went
son you can't split the project up into two projects? A
> java8 => js frontend, and the java7 backend?
>
> On 03/09/2016 02:57 PM, Paul Mazzuca wrote:
>
> Using the maven gwt and appengine plugins, is it possible to compile GWT
> 2.8 in Java 8, and then app engine related files us
ava 7? I
realize the managed VMs support Java 8, but it would be nice to stick
with the app engine environment which currently only support Java 7?
I am wondering if there exists some maven configuration that would
first compile all the GWT files in Java 8, thereby converting them to
javascr
Using the maven gwt and appengine plugins, is it possible to compile GWT
2.8 in Java 8, and then app engine related files using Java 7? I realize
the managed VMs support Java 8, but it would be nice to stick with the app
engine environment which currently only support Java 7?
I am wondering
migrate to Dagger 2 anytime soon
>> (especially not if it takes ages for a PR to be accepted).
>>
>
> So they probably won't migrate to GWT 2.8 either.
>
>
>> Anyways any generator that tries to load JDT generated classes while
>> being executed with
, and the user does not bother about the sourceLevel flag.
>
>
>
> On Wed, Feb 17, 2016 at 9:13 PM, 'Goktug Gokdogan' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> I think you didn't understand what I said. Let me try to clarif
sounds like "unmaintained" to me.
> A lot of these apps will probably not migrate to Dagger 2 anytime soon
> (especially not if it takes ages for a PR to be accepted).
>
So they probably won't migrate to GWT 2.8 either.
> Anyways any generator that tries to load JD
On Wednesday, February 17, 2016 at 9:13:43 PM UTC+1, Goktug Gokdogan wrote:
>
> I think you didn't understand what I said. Let me try to clarify:
>
> "For any reason, if community wants to run the GWT 2.8 SDK in Java 7
> source level *(i.e. gwtc sourcelevel 7)*, they
accepted).
Anyways any generator that tries to load JDT generated classes while being
executed with Java 7 will fail. I wouldn't bet that GIN is the only library
affected. I just wanted to note that the current situation is not "GWT 2.8
is fully compatible to Java 7", its more like
of month at the time Guava 21 will be released (mid 2016, requires Java 8).
> So I am not sure if its worth it to buy people a couple of extra month of
> 1.7 support.
>
> Alternatively we could also make two releases 2.7.1 and 2.8 with 2.7.1
> containing everything of 2.8 up
;> compiled with sdk7, and the user does not bother about the sourceLevel flag.
>>
>>
>>
>> On Wed, Feb 17, 2016 at 9:13 PM, 'Goktug Gokdogan' via GWT Contributors <
>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>
>>> I
ributors@googlegroups.com> wrote:
>
>> I think you didn't understand what I said. Let me try to clarify:
>>
>> "For any reason, if community wants to run the GWT 2.8 SDK in Java 7
>> source level *(i.e. gwtc sourcelevel 7)*, they can theoretically do it
>
mmunity wants to run the GWT 2.8 SDK in Java 7
> source level *(i.e. gwtc sourcelevel 7)*, they can theoretically do it by
> supplying *a java7 compatible JRE emulation* without any compiler/SDK
> changes *(but just setting the gwtc sourcelevel 7)*. That's why I didn't
> ori
I think you didn't understand what I said. Let me try to clarify:
"For any reason, if community wants to run the GWT 2.8 SDK in Java 7 source
level *(i.e. gwtc sourcelevel 7)*, they can theoretically do it by
supplying *a java7 compatible JRE emulation* without any compiler/SDK
changes *(but
ompiled in Java7 mode.
>
> However, GWT compiler itself is intended to be runnable in a Java 7 JVM.
> This should enable slow-to-upgrade enterprises business to keep their
> legacy dev environments.
> For any reason, if community wants to run the GWT 2.8 SDK in Java 7 source
> level, th
To remind the backlog of this:
GWT 2.8 decided to support only Java8 source level (see related threads
from last year) as the emulation will include Java 8 APIs which cannot be
compiled in Java7 mode.
However, GWT compiler itself is intended to be runnable in a Java 7 JVM.
This should enable
On Monday, February 15, 2016 at 11:39:02 AM UTC+1, Thomas Broyer wrote:
>
>
>
> On Monday, February 15, 2016 at 10:06:47 AM UTC+1, Manuel Carrasco Moñino
> wrote:
>>
>> Thomas, I want to experiment with this, pls, could you give me some
>> advise what are the classes I have to look at?
>>
>
>
this discussion
>>> started in the maintainer list to the contributors one. Feel free to
>>> contribute with your opinions.
>>> Basically the matter is about the convenience of not breaking java7
>>> compatibility in 2.8
>>>
>>> Thanks
>>
lo
>>
>> On Fri, Feb 12, 2016 at 6:14 PM, Thomas Broyer <t.bro...@gmail.com>
>> wrote:
>>
>>> FWIW, I just tried the latest snapshot (from today) with Java 7 and it
>>> seems to work (for now; see below).
>>> I think the issue in the samp
-Manolo
>
> On Fri, Feb 12, 2016 at 6:14 PM, Thomas Broyer <t.bro...@gmail.com> wrote:
>
>> FWIW, I just tried the latest snapshot (from today) with Java 7 and it
>> seems to work (for now; see below).
>> I think the issue in the samples is with -sourceLevel: th
, 2016 at 6:14 PM, Thomas Broyer <t.bro...@gmail.com> wrote:
> FWIW, I just tried the latest snapshot (from today) with Java 7 and it
> seems to work (for now; see below).
> I think the issue in the samples is with -sourceLevel: the POMs there set
> maven.compiler.source to 1.7, w
t;>> require Java8. If someone needs Java7 support they need to replace the
>>> emulation code of GWT 2.8 with the one of GWT 2.7. Because of this
>>> possibility we don't use Java8 APIs in gwt-user code. gwt-servlet.jar
>>> is something to think about as soon as we want to a
need to replace the
>> emulation code of GWT 2.8 with the one of GWT 2.7. Because of this
>> possibility we don't use Java8 APIs in gwt-user code. gwt-servlet.jar
>> is something to think about as soon as we want to add GWT-RPC
>> serializer for Java 8 classes. If we really wan
includes Java 7 grammar support, which is now supported
(and the default) in gwt 2.6.0+.*
*In order to upgrade the current .xml configuration files for Checkstyle,
the following appear to be needed:*
*PackageHtml* looks like it can just be changed to *JavadocPackage*.
*GenericIllegalRegexp
Awesome. Looks like you got all of the changes that I had found, plus you
cleaned up a ton of the code as well. This is extremely helpful!
On Saturday, June 7, 2014 2:55:36 PM UTC-4, Roberto Lublinerman wrote:
We upgraded to checkstyle 5.7 in trunk (
.
*Checkstyle 5.7 includes Java 7 grammar support, which is now supported
(and the default) in gwt 2.6.0+.*
*In order to upgrade the current .xml configuration files for Checkstyle,
the following appear to be needed:*
*PackageHtml* looks like it can just be changed to *JavadocPackage
I resolved this. In combination of explictly setting the source level
target to the Java and GWT compilers, I had to delete the gwt-unitCache
directory as well.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this
I've recently updated my GWT project to 2.6.1, and started to make use of
Java 7 syntax since 2.6 now supports Java 7.
However, when I attempt to compile, I'm receiving compiler errors such as
[ERROR] Line 42: '' operator is not allowed for source level below 1.7
Full output
Compiling
Probably worth nothing that I can compile and run the project just fine
through the IntelliJ run configurations. It's just when I attempt to
compile via the Ant targets (either within IntelliJ or at a system command
line) that I have issues.
--
You received this message because you are
Something like ;
switch (book) {
case Harry Potter:
break;
case Hitch Hikers Guide To The Galaxy:
break;
Should now work with the latest GWT from here;
https://code.google.com/p/google-web-toolkit/downloads/list
Correct?
Because I am still getting a[ERROR] Line 1971: Cannot switch on a
Have I somehow setup GWT 2.6 wrongly?
Using switch() with strings works in GWT 2.6. I guess you have to double
check your setup. Maybe you have used an old run configuration that is not
up-to-date?
-- J.
--
You received this message because you are subscribed to the Google Groups
Ah, Bingo...it was either down to not clearing the cache's, or the fact a
non-GWT 2.6 project was being inherited in.
Fixing both of those and it works.
*goes of to enjoy Java7*
~~~
Thomas Bertines online review show:
http://randomreviewshow.com/index.html
Try it! You might even feel ambivalent
/user/test/com/google/gwt/
event/dom/client/DomEventTest.java
Leeroy has commented some strange EOF errors. I have then removed the
diamond operator and he seems to be happy again.
Is this a bug or is it not yet allowed to use Java 7 syntax in GWT source?
Those come from checkstyle, of which we
I see. Thanks for the information.
-- J.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
the
diamond operator and he seems to be happy again.
Is this a bug or is it not yet allowed to use Java 7 syntax in GWT source?
-- J.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
/DomEventTest.java
Leeroy has commented some strange EOF errors. I have then removed the
diamond operator and he seems to be happy again.
Is this a bug or is it not yet allowed to use Java 7 syntax in GWT source?
Those come from checkstyle, of which we use an old version that predates
Java 7. That said
Ray Cromwell has posted comments on this change.
Change subject: Adds part of Java 7 new language features.
..
Patch Set 10: Code-Review+2
(1 comment)
File
dev/core/src
Ray Cromwell has posted comments on this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Patch Set 8: Code-Review+2
(1 comment
Roberto Lublinerman has posted comments on this change.
Change subject: Adds part of Java 7 new language features.
..
Patch Set 10:
(1 comment)
Thanks.
File
dev/core
Roberto Lublinerman has posted comments on this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Patch Set 8:
(1 comment)
Thanks for this as well
Hello Matthew Dempsky, Ray Cromwell, Matthew Dempsky, Leeroy Jenkins,
Goktug Gokdogan,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2681
to look at the new patch set (#9).
Change subject: Adds the remaining (and more complex) Java 7 new language
Roberto Lublinerman has posted comments on this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Patch Set 9:
Previous patch was approved and changes since then are trivial
Roberto Lublinerman has posted comments on this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Patch Set 9: Code-Review+2
Previous patch was approved and changes since
Roberto Lublinerman has posted comments on this change.
Change subject: Adds part of Java 7 new language features.
..
Patch Set 8:
Ping.
--
To view, visit https://gwt-review.googlesource.com/2650
To unsubscribe, visit https
Roberto Lublinerman has posted comments on this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Patch Set 6:
Ping.
--
To view, visit https://gwt-review.googlesource.com/2681
Matthew Dempsky has posted comments on this change.
Change subject: Adds part of Java 7 new language features.
..
Patch Set 8:
I assume you're pinging for John and/or Ray?
--
To view, visit https://gwt
Brian Slesinsky has posted comments on this change.
Change subject: Adds part of Java 7 new language features.
..
Patch Set 8: Code-Review+1
(7 comments)
Looks fine to me. I have a few nits, but they don't need to be fixed
Hello Matthew Dempsky, Matthew Dempsky, Leeroy Jenkins, Goktug Gokdogan,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2681
to look at the new patch set (#7).
Change subject: Adds the remaining (and more complex) Java 7 new language
features
Hello Matthew Dempsky, Matthew Dempsky, Leeroy Jenkins, Brian Slesinsky,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2650
to look at the new patch set (#9).
Change subject: Adds part of Java 7 new language features
Roberto Lublinerman has posted comments on this change.
Change subject: Adds part of Java 7 new language features.
..
Patch Set 8:
(7 comments)
@Ray, can you have a look at this patch and its successor and if ok +2 them
Hello Matthew Dempsky, Matthew Dempsky, Leeroy Jenkins, Brian Slesinsky,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2650
to look at the new patch set (#10).
Change subject: Adds part of Java 7 new language features
Hello Matthew Dempsky, Matthew Dempsky, Leeroy Jenkins, Goktug Gokdogan,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2681
to look at the new patch set (#8).
Change subject: Adds the remaining (and more complex) Java 7 new language
features
Brian Slesinsky has posted comments on this change.
Change subject: Adds part of Java 7 new language features.
..
Patch Set 10: Code-Review+1
--
To view, visit https://gwt-review.googlesource.com/2650
To unsubscribe, visit
Hello Matthew Dempsky, Leeroy Jenkins,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2650
to look at the new patch set (#8).
Change subject: Adds part of Java 7 new language features
Hello Matthew Dempsky, Matthew Dempsky, Leeroy Jenkins, Goktug Gokdogan,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2681
to look at the new patch set (#6).
Change subject: Adds the remaining (and more complex) Java 7 new language
features
Hello Matthew Dempsky, Leeroy Jenkins,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2681
to look at the new patch set (#4).
Change subject: Adds the remaining (and more complex) Java 7 new language
features
Hello Matthew Dempsky, Leeroy Jenkins,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2681
to look at the new patch set (#5).
Change subject: Adds the remaining (and more complex) Java 7 new language
features
Roberto Lublinerman has uploaded a new patch set (#5).
Change subject: Adds part of Java 7 new language features.
..
Adds part of Java 7 new language features.
Adds the Java 7 new language features: namely, the diamond
Roberto Lublinerman has abandoned this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Abandoned
Redid as dependent patch.
--
To view, visit https://gwt
Matthew Dempsky has posted comments on this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Patch Set 1: Verified-1
Oops, this change failed the build and/or style presubmit
Matthew Dempsky has posted comments on this change.
Change subject: Adds part of Java 7 new language features.
..
Patch Set 5: Verified+1
Hoorays, this change passed the build and style presubmit. :D More details
at http
Matthew Dempsky has posted comments on this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Patch Set 1:
(1 comment)
File
Goktug Gokdogan has posted comments on this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Patch Set 1:
(9 comments
Hello Matthew Dempsky,
I'd like you to reexamine a change. Please visit
https://gwt-review.googlesource.com/2681
to look at the new patch set (#2).
Change subject: Adds the remaining (and more complex) Java 7 new language
features
Matthew Dempsky has posted comments on this change.
Change subject: Adds the remaining (and more complex) Java 7 new language
features.
..
Patch Set 2: Verified+1
Hoorays, this change passed the build and style presubmit
Roberto Lublinerman has uploaded a new patch set (#3).
Change subject: Adds Java 7 new language features.
..
Adds Java 7 new language features.
Adds the Java 7 new language features: namely, the diamond operator, new
Roberto Lublinerman has uploaded a new patch set (#4).
Change subject: Adds part of Java 7 new language features.
..
Adds part of Java 7 new language features.
Adds the Java 7 new language features: namely, the diamond
Roberto Lublinerman has posted comments on this change.
Change subject: Adds Java 7 new language features.
..
Patch Set 1:
This patch includes the JDT 3.8 update patch; I am uploading to start the
review process
Matthew Dempsky has posted comments on this change.
Change subject: Adds Java 7 new language features.
..
Patch Set 1:
Are the JDT 3.8 jars that you want to use stable? If so, maybe we should
go ahead and add those
Matthew Dempsky has posted comments on this change.
Change subject: Adds Java 7 new language features.
..
Patch Set 1:
Oh, disregard that comment then. Didn't realize this was the child
patch. :)
--
To view, visit https
Roberto Lublinerman has uploaded a new patch set (#2).
Change subject: Adds Java 7 new language features.
..
Adds Java 7 new language features.
Adds the Java 7 new language features: namely, the diamond operator, new
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
).
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
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
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
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
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.
2.5 rc2 should run on a JDK 7 virtual machine (there was a recent fix
to make dev mode work). We've occasionally talked about supporting Java 7
features, but there's no concrete plan or schedule to implement them.
- Brian
On Tuesday, September 25, 2012 4:38:28 AM UTC-7, Benjamin Wolff wrote
Em quinta-feira, 21 de fevereiro de 2013 09h32min44s UTC-3, Seamus McMorrow
escreveu:
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 JDK7
I am using GWT 2.5, and wondering if many people are using JDK7 in
On Thursday, February 21, 2013 1:32:44 PM UTC+1, Seamus McMorrow wrote:
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 JDK7
I am using GWT 2.5, and wondering if many people are using JDK7 in their
fix
to make dev mode work). We've occasionally talked about supporting Java 7
features, but there's no concrete plan or schedule to implement them.
- Brian
On Tuesday, September 25, 2012 4:38:28 AM UTC-7, Benjamin Wolff wrote:
Hi,
sorry for gravedigging, but the title of this thread seems
When does 2.5 rc2 will be available to download?
Thanks,
Krzysztof
On Tuesday, 25 September 2012 22:21:26 UTC+1, Brian Slesinsky wrote:
GWT 2.5 rc2 should run on a JDK 7 virtual machine (there was a recent fix
to make dev mode work). We've occasionally talked about supporting Java 7
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
--
You received
GWT 2.5 rc2 should run on a JDK 7 virtual machine (there was a recent fix
to make dev mode work). We've occasionally talked about supporting Java 7
features, but there's no concrete plan or schedule to implement them.
- Brian
On Tuesday, September 25, 2012 4:38:28 AM UTC-7, Benjamin Wolff
Hi everyone,
The following error is returned when compiling code using the diamond
operator (part of project coin in Java 7).
Syntax error on token , ? expected after this token
I am using the GWT 2.40 (Plugin -
com.google.gwt.eclipse.sdkbundle_2.4.0.v201205091048-rel-r37).
The following
On Thursday, June 14, 2012 12:49:55 PM UTC+2, Albert Attard wrote:
Question:
1. Does GWT support Java 7 features?
No.
Not yet. Though it will likely take some time.
1. What changed do I need to perform in order to have the Java 7 code
working without having to change
Thanks for your reply.
Albert
On Thursday, June 14, 2012 12:57:36 PM UTC+2, Thomas Broyer wrote:
On Thursday, June 14, 2012 12:49:55 PM UTC+2, Albert Attard wrote:
Question:
1. Does GWT support Java 7 features?
No.
Not yet. Though it will likely take some time.
1. What
:(. There are plenty of posts about
this.
Thanks again,
Albert Attard
On Thursday, June 14, 2012 12:57:36 PM UTC+2, Thomas Broyer wrote:
On Thursday, June 14, 2012 12:49:55 PM UTC+2, Albert Attard wrote:
Question:
1. Does GWT support Java 7 features?
No.
Not yet. Though it will likely
Just stumbled on that:
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.
— *Source: *
On Jul 5, 1:21 am, Magno Machado magn...@gmail.com wrote:
Is there any current work on supporting java 7 syntax on gwt? Will it be
available on GWT 2.4?
I think this question is of general interest. But as nobody replied
yet, I suppose not :(
-Alex
--
You received this message because you
Well, GWT uses Eclipse's JDT (a patched version AFAIK), so it would first
have to be updated to a version that supports Java 7, and then GWT code
updated to support the changes (such as mapping switch on strings to the
same switch on strings construct in JavaScript).
…but Eclipse's JDT support
it'll
be faster for Java 7, but don't be too impatient IMO.
Are you sure this is true? I thought 1.6 is supported as of 2.3, but not
required. 1.6 will be required in future releases of GWT however (it may be
required for 2.3, i'm not sure) but I know commits to trunk are going in
with @Override
GWT requiring a Java6 JVM is different from officially supporting Java 6
language features in what the GWT Compiler accepts as input ;-)
(I believe Java 6 is supported –as I said, at least some features already
are, for quite some time, and I've almost always been using Java 6
compliance level
Java 7 is going to be released in a few days and will introduce some changes
on the java syntax
Is there any current work on supporting java 7 syntax on gwt? Will it be
available on GWT 2.4?
--
Magno Machado Paulo
http://blog.magnomachado.com.br
http://code.google.com/p/emballo/
--
You
Hello,
is it possible to use Java 7 in GWT ?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit
come in, I still like the
command pattern...
Regards
Sebastian
On Jul 19, 8:15 pm, dolcra...@gmail.com dolcra...@gmail.com wrote:
I think GWT should refrain from including Java 7 features until it is
released at least...
On Jul 19, 1:48 pm, Daniel Simons daniel.simo...@gmail.com wrote:
Hey
1 - 100 of 104 matches
Mail list logo
