GWT 2.8.0 released

['Daniel Kurka' via GWT Users]

Hi all,

I am very happy to announce GWT 2.8.0 on behalf of the GWT steering 
committee and the GWT team at Google.

You can download the release from http://www.gwtproject.org/download.html 
or from maven central.

The release notes can be found at 
http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0

Daniel,
on behalf of the GWT team

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT 2.8.0 RC2 is here!

['Daniel Kurka' via GWT Users]

Hi all,

I just build the GWT 2.8.0 RC2 and pushed it to maven central. The complete 
SDK is also available from here .

Please start testing and let us know if you run into any trouble and file 
bugs .

We are planing to release this as GWT 2.8.0 if we do not here about any 
serious issues within the next two weeks. The release notes for RC 
2
 will 
be made available shortly after this notice, in the mean time you can take 
a look at the github repository 

.

Daniel,
on behalf of the GWT team

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

2.8.0 RC1 is here!

['Daniel Kurka' via GWT Users]

Hi all,

I just build the GWT 2.8.0 RC1 and pushed it to maven central. The complete 
SDK is also available from here .

Please start testing and let us know if you run into any trouble. You can 
either reply to this thread on gwt-contrib 

 or file bugs .

We are planing to release this as GWT 2.8.0 if we do not here about any 
serious issues within the next two weeks. The release notes for RC1 

 
will be made available shortly after this notice, in the mean time you can 
take a look at the github repository 

.

Daniel,
on behalf of the GWT team

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT no longer working with Chrome 49

['Daniel Kurka' via GWT Users]

About production issue: Are you sure about this? It's less likely to happen 
in production since many clinit calls will have been stripped by the 
compiler, but its probably still going to happen.

About development: Is there actually a global try catch in your code or is 
this even something else? I am not really familiar with the old GWT linkers 
anymore and how they outputted code.

On Wednesday, April 6, 2016 at 4:47:45 PM UTC+2, TazmanianD wrote:
>
> Thanks so much for the response! You say "all modern versions of GWT". I 
> don't suppose you can be more specific? The 2.8 version hasn't been 
> released yet and we can't upgrade to pre-release versions. We can probably 
> give the beta version a try just to see if it does fix our problem. Is this 
> problem fixed in 2.7? We've been waiting for 2.8 before undertaking the 
> upgrade but it sounds like we need to jump to 2.7 now.
>
> Fortunately for us, this isn't (apparently) a production issue for us yet 
> so we're not in an emergency mode but I gather others may not be so lucky. 
> I posted a reply to a question in the Chrome forum where someone was using 
> GWT 1.6 and upgrading may be even harder for this. I don't suppose you have 
> any other advice for anyone else who may stumble across this and not have 
> an immediate path to upgrade?
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT no longer working with Chrome 49

['Daniel Kurka' via GWT Users]

Hi,

Chrome 49 enabled lots of ES6 features, 
see: http://v8project.blogspot.de/2016/01/v8-release-49.html

Part of this is the so called sloppy function hosting.

A simple example:


ES5 (old semantics)

ES2015 (new semantics)

Code

try {

 function foo() {

   foo=function(){};

   console.log('hello');

 }

} catch(e) { }

foo(); // overwrites behavior

foo(); // no-op

try {

 function foo() {

   foo=function(){};

   console.log('hello');

 }

} catch(e) { }

foo(); // does not overwrite

foo();

Output

hello

hello

hello


The problem here is the presence of the try catch block and that semantics 
have changed here.
We investigated this a few months back and all modern versions of GWT 
should not be impacted.

So my first recommendation would be to upgrade to GWT 2.8-beta1 and see if 
the issue still exists for you.
 


On Tuesday, April 5, 2016 at 9:38:28 PM UTC+2, TazmanianD wrote:
>
> I'm duplicating a comment I made in the Chrome group but I thought I 
> should cross-post it here as well. We're using GWT 2.5.0 and we're 
> suddenly experiencing massive errors as well although fortunately for us, 
> they only seem to be affecting our development env and not production.
>
> In our case, what I've discovered is that the static initializers for 
> *some* classes are being executed repeatedly. This is fatal for enums as 
> the enum values are recreated each time and they're supposed to be 
> singletons. The result is that EnumMaps for those enums don't work at all. 
> In debugging the code, I found that when the static initializer function 
> reassigns itself to the null function, this works in the function but when 
> the function returns, the function pointer is reset back to where it was 
> originally pointing. This means that next time the initializer is executed, 
> instead of it being a no-op, it runs again. I almost wonder if there's some 
> sort of scope confusion and the function assignment is assigning to the 
> wrong or duplicate function.
>
> And another thing I'll note is that we have soft-permutations enabled in 
> our dev env and when we disable those and generate separate permutations, 
> the problem goes away. I don't see how that can explain what I saw in my 
> debugger but I thought it was worth mentioning.
>
> Unfortunately my attempts at reducing the problem to a simple case have 
> totally failed as when I delete too much, the problem seems to disappear. 
> This unfortunately makes my report here not terribly useful but maybe 
> others can chime in if their seeing the same thing.
>
> But let me try to summarize with some pseudo-code (a simple example like 
> this does *not* exhibit the problem):
>
>
> class MyEnum {
>   static {
> Window.alert("Static Initializer");
>   }
>
>   public void foo() {...}
> }
>
>
> MyEnum instance = new MyEnum();
> instance.foo();
>
> -- When this code is run the alert "Static Initializer" is displayed twice 
> (or more if you have additional usages)
>
> --- Get's compiled into (approximately):
>
> var instance = $clinit$MyEnum(), new MyEnum();
> $clinit$MyEnum(), instance.foo();
>
> function $clinit$MyEnum() {
>   $clinit$MyEnum() = nullFunction; // Disables the static initializer so 
> it doesn't run again
>   $wnd.alert("Static Initializer");
> }
>
> -- What I see in the Chrome debugger is that when $clinit$MyEnum is 
> assigned to the nullFunction, the watch immediately reflects this. However 
> the moment you step back out of the function, the value of "$clinit$MyEnum" 
> returns to the original function.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.