Hi Thomas - That was the missing piece. I can now get the automatic re-compile on browser refresh. However, the launcherDir parameter is only available in the gwt-maven-plugin:run-codeserver mojo. Doesn't that start Super Dev Mode directly? I thought that *wasn't* the correct way to do things in a 2.7+ world.
I'm pretty confused about how we should be debugging GWT apps at this point - maybe it's just a terminology thing. Best I can tell, the GWT Super Dev Mode CodeServer is now launched either explicitly (using the CodeServer main or from the gwt-maven-plugin:run-codeserver mojo) OR implicitly by using the gwt-maven-plugin:run mojo (which starts DevMode, but now defaults to SuperDevMode and starts the code server). Is that accurate? If so, it seems like the <launcherDir> parameter should be added to the run mojo, no? On Tuesday, April 12, 2016 at 6:23:48 PM UTC-4, Thomas Broyer wrote: > > If you were already using CodeServer, then just add -launcherDir pointing > to the exploded war folder in your Tomcat. This will generate a new > nocache.js overwriting the original one that will trigger SDM on load, so > you have nothing to do but load your app. -- You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
