Separate compilation mentioned in your linked issue has been reworked into incremental per file compilation what you have now with GWT 2.7. The benefit is that people do not have to refactor their applications into multiple modules to get the benefit of faster recompiles in SDM.
Regarding CodeServer restarts: With current GWT master branch, a restart of the CodeServer reuses the caches from the last compile which reduces the startup time of CodeServer significantly. Keep in mind that you do not have to use the DevMode class to start the embedded Jetty + Code Server process. You can also split these processes so you do not have to restart SDM CodeServer if you do a server side change. DevMode -noserver or launching CodeServer directly only starts the SDM code server. Then you can provide your own application server or actually start DevMode -nosuperdevmode which does start classic DevMode but also the embedded Jetty for your server side code. I rarely restart CodeServer during the work day. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
