Re: module.nocache.js generated with same timestamp as module.gwt.xml
I have just noticed this same issue, and am glad to have found Dop Sun's post here. Thanks Thomas for the link to the proposed path. I notice on Jan 6 the patch was merged, but then reverted later that day, because *need to update some tests before committing this change*. I hope this hasn't been forgotten and it will make the next release of GWT? Thanks, Rob On Wednesday, December 31, 2014 at 5:47:19 PM UTC+11, Dop Sun wrote: Thanks Thomas. On Wednesday, December 31, 2014 2:33:59 AM UTC+8, Thomas Broyer wrote: 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 http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#DevGuideCompilerOptions, 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+unsubscr...@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.
module.nocache.js generated with same timestamp as module.gwt.xml
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 http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#DevGuideCompilerOptions, 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+unsubscr...@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.
Re: module.nocache.js generated with same timestamp as module.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 http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#DevGuideCompilerOptions, 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+unsubscr...@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.
Re: module.nocache.js generated with same timestamp as module.gwt.xml
Thanks Thomas. On Wednesday, December 31, 2014 2:33:59 AM UTC+8, Thomas Broyer wrote: 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 http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#DevGuideCompilerOptions, 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+unsubscr...@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.
