On Tuesday, September 19, 2017 at 5:30:11 PM UTC+2, Jens wrote: > > IMHO it is preferable to launch SuperDevMode and your server (be it jetty > or anything else) separately so you can restart them separately. We do that > at work and only rarely restart SuperDevMode. >
I wholeheartedly agree, but even when using the embedded Jetty container in DevMode, you can restart the webapp without restarting DevMode. > Generally restarting SuperDevMode in GWT 2.8.x works better as GWT 2.8.x > stores a cache on disk that can be reused between restarts. Also GWT 2.8.x > SuperDevMode only recompiles code that has been modified when you reload > the browser. GWT 2.7. always recompiles the whole app when using the > bookmarklets to recompile your code. So generally GWT 2.8.x SuperDevMode > should work faster in terms of recompilation. > Hey Jens, nobody should use the bookmarklets in 2.7 either ;-) But yes, as I said in https://github.com/gwtproject/gwt/issues/9549#issuecomment-330555850, 2.8 (or HEAD-SNAPSHOT) should work better *and* would be the basis for a fix/improvement if ever needed, so the first thing to do is (always) updating to the latest version (and trying HEAD-SNAPSHOT too if you can). -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
