On Wednesday, April 6, 2016 at 10:18:04 PM UTC+2, Vassilis Virvilis wrote: > > 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. >
FWIW, for Maven users, net.ltgt.gwt.maven:gwt-maven-plugin has a workaround for it: https://github.com/tbroyer/gwt-maven-plugin/blob/1.0-rc-6/src/main/java/net/ltgt/gwt/maven/CompileMojo.java#L229-L234 -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
