*.nocache.js file with old lastmodified date

[christia...@gmail.com]

Hello,

compiling a GWT module causes the last-modified date of the "*.nocache.js" file is set to the last-modified date of the "*.gwt.xml" file.

If using eclipse with tomcat you are running in problems. All files - except the nocache.js - are copied to tomcat working directory. The nocache.hs file is not copied, because its last-modified timestamp is not updated.

Problem exists in GWT 2.7.0 running on OSX 10.10. Current workaround is to overwrite the "emitSelectionScript" in a custom linker:

@Override
protected EmittedArtifact emitSelectionScript(TreeLogger logger, LinkerContext context, ArtifactSet artifacts) throws UnableToCompleteException {
 String ss = generateSelectionScript(logger, context, artifacts);
 return emitString(logger, ss, context.getModuleName() + ".nocache.js");
 }

Because this was working in GWT 2.6.0 we think it is a bug in GWT 2.7.0.

Thanks

Christian

[John Stalcup]

addressing this at https://gwt-review.googlesource.com/#/c/10520/

--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/5f62e34b-6260-45b9-8ced-f9e1897cf353%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[christia...@gmail.com]

Thanks!

When updating the version we can "fix" our custom linker.

Thanks

Christian

[Ernesto Guimerans]

Same issue here after updating to GWT 2.7.0. Last release I have been working with, GWT 2.6.1, worked properly.

Cheers, 

[Denis A.]

@John Stalcup: You reverted the fix for this issue here:

https://gwt.googlesource.com/gwt/+/f876c6c4de627adcdcec891e013fd27354d0380f
so this issue stroke back:
https://github.com/gwtproject/gwt/issues/9108

can you elaborate on why you reverted this fix and on the proper way to reintroduce it (the GitHub issue reporter may be interested in your response too)?

Regards,

Denis