This is a known problem for 2.7 I think it is fixed for 2.8
https://github.com/gwtproject/gwt/issues/9108 So far I am touching the nocache.js after deployment as a workaround (otherwise all clients have to to Shift+Reload to get the changes and then there is the fun with the different caching behavior per browser). I think this kind of bugs warrant a 2.7.x release. Death by paper cut is what comes to mind. I mean it's not really important but it causes pain in a surprising manner. On Wed, Apr 6, 2016 at 10:59 PM, Mike Warne <mike.wa...@gmail.com> wrote: > Hi, > I am having an issue where my nocache.js file timestamp seems to be locked > to the GWT.xml module file timestamp. > So it is difficult to see changes when the app is deployed. > > > I am using the GWT plugin for eclipse, with GWT 2.7.2.0 > I noticed there was a bug fix for this in the GWT project. > > Is this fix included in this version of GWT? > > Sorry if this is the wrong forum for this, but I though someone here might > have faced this issue also.. > > Thanks, > Mike. > > -- > 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. > -- Vassilis Virvilis -- 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.
