Re: .nocache.js generated with same timestamp as .gwt.xml

This is actually a known issue with a proposed patch: https://gwt-review.googlesource.com/10520

On Tuesday, December 30, 2014 5:04:05 PM UTC+1, Dop Sun wrote:

Hi,

In previous versions, e.g. 2.6.1, <module>.nocache.js file generated with timestamp when the files generated. But in version 2.7.0, the <module>.nocache.js file generated with the same timestamp of <module>.gwt.xml.

Is this by design? 

I'm raising this question because it causes Safari ignores latest compiled <module>.nocache.js (which is same timestamp as <module>.gwt.xml), and using previously cached file, which is compiled by 2.6.1, and causing application not working in Safari.

And yes, suggestions of this page, section [Perfect Cache] can help. Change .htaccess file with suggested expiry settings.

I'm using Mac OS X Yosemite.

Thanks,

Regards,

Dop

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