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

2015-02-18 Thread Rob Newton
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

module.nocache.js generated with same timestamp as module.gwt.xml

2014-12-30 Thread Dop Sun
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

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

2014-12-30 Thread Thomas Broyer
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

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

2014-12-30 Thread Dop Sun
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,