Nope - even though Dev Mode runs now and goes into Super Dev Mode, our application is not actually loading in SDM when we visit the web page.
Our web serving and resources are bundled into JARs, so I suspect the idea of overwriting the .nocache.js is just flawed or not working for this mode. There is no .nocache.js existing in the file system which overwriting will change our application behaviour. SDM does still work for us if run explicitly, but we have to add a -noincremental flag, which I think defeats any speed gains On Friday, 5 December 2014 11:42:48 UTC+2, Rob Walker wrote: > > Sadly the -launcherDir won't work for us I don't think - we're running an > embedded Felix/OSGi server which serves up our application from bundle > JARS. So there is no dir we can point them at. > > As per thread below, I think I am making progress with Dev Mode launch > though - at least it is actually launching now anyhow. Seemed to need quite > a few command line mods from our original BAT file to launch Dev Mode > > On Friday, 5 December 2014 11:31:55 UTC+2, Thomas Broyer wrote: >> >> >> >> On Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote: >>> >>> I'm really not surprise people are hitting this issue. It's not clear >>> (or wasn't to me) from the Release Notes that you no longer run Super Dev >>> Mode from the standalone program in 2.7 as was done in 2.6, but that >>> running via Dev Mode enables it. >>> >> >> …or you can keep your launcher with CodeServer but add a -launcherDir >> argument pointing to the folder your standalone server is serving. >> CodeServer will then generate a .nocache.js in there that enables "compile >> on load". >> >> And yes the docs need an update (and I wasn't even aware of the issue >> with the bookmarklets; good to know, and I believe we should try to fix it >> because it can be really handy) >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/fd93475e-ac71-4455-824a-a46d87d5e3c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
