GWT 2.7 + GAE app looks for codeserver when deployed

Question

Why does appengine try to use Super Dev Mode?

Every time I deploy my GWT app to appengine and try to access it I get the white loading screen, then after about 20-

Answer 1

gwt:compile tries to work "incrementally" by comparing the timestamp of the nocache.js file with the ones of the source files, and skipping GWT compilation if it thinks the output is up-to-date. This is brittle though. gwt:run (without <superDevMode>false</superDevMode>; and gwt:run-codeserver with launcherDir) will overwrite the nocache.js with a SuperDevMode-specific version, and this is likely to lead to gwt:compile skipping the compilation.

The takeaway is: when deploying or "releasing", make sure you first run mvn clean or force gwt:compile to run by passing -Dgwt.compiler.force to Maven.

Answer 2

Just for information, I had the same problem, caused by the usage of a non-standard project structure.

Maven was copying the .nocache files in a directory different than /target/which prevented the clean plugin from cleaning the generated files.

Adding a new with the directory where the files are copied solves the problem.