Re: 2.7.0 and module.nocache.js

DevMode's new behavior of using SuperDevMode by default, the nocache.js has to contain the necessary bits to trigger "compile on load".

When running DevMode with -nosuperDevMode though, there's a regression in 2.7: https://code.google.com/p/google-web-toolkit/issues/detail?id=9021

On Wednesday, December 3, 2014 6:57:12 PM UTC+1, Nathan wrote:

In GWT 2.7.0-rc1 and earlier versions, I was able to compile my application and then launch the GWT development shell in devmode version and have it serve up the normal compiled version of my application as well as use devmode if I wanted (from supported browsers). However, now it seems that running devmode causes the module.nocache.js file to be replaced and gives a message "GWT module may need to be (re)compiled" when trying to access the normal compiled version. If I then replace module.nocache.js with the version generated from compiling, both devmode and the normal compiled mode work. Is there a reason this change was made to have devmode replace module.nocache.js on start up breaking compiled mode?
-Nathan

--
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.
For more options, visit https://groups.google.com/d/optout.