Same behaviour with -draftCompile, I've also tried optimizationLevel to 0
Le mercredi 30 décembre 2015 00:35:12 UTC+1, Jens a écrit :
-- Le mercredi 30 décembre 2015 00:35:12 UTC+1, Jens a écrit :
I think it does not look too bad. You can compile your app using -mode PRETTY (or DETAILED if you also need package infos) so you can read the final JS output to see what went wrong. The only difference between SuperDevMode and a normal compile is that a normal compile optimizes your code. When you do a normal compile using -draftCompile then its pretty similar to SuperDevMode. When it works this way then you have probably found a bug caused by optimizations.-- J.
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+unsubscribe@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.
No comments:
Post a Comment