Re: GWT 2.7.0 is here

On Tuesday, February 17, 2015 at 3:54:35 PM UTC-8, Jens wrote:

When you start DevMode -war /path/to/war/ then GWT 2.7 will generate a <module>.nocache.js file in the specified war folder. However it does not override any existing <module>nocache.js file. So the best thing you can do is to delete your old /path/to/war/<module> folder so that you start with a fresh one generated by GWT 2.7. After SDM has started you can deploy the war and recompile on reload should work.

The above also means that if you build a production version of your app you should first clean that folder again so you do not accidentally deploy a generated <module>.nocache.js file into production that was actually meant to be used with SDM only.

-- J.

Thanks for your info. I clean the war/client dir and then launch SDM but still the launch page http://127.0.0.1:8888/module.html still cannot load client/module.nocache.js file although the module.nocache.js file is really under war/client/module.nocache.js. This is Tomcat server, does SDM create other server than Jetty different?
I did a test to manually rename the module.nocache.js to module-nocache.js file and upate module.htmi to load client/module-nocache.js file, it works. How come?

--
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.