We have experienced this a bit and have a custom script to clean out the cache although it seems we could have just used the SDM UI.
However the most frequent place we find this is on inline lambdas. i.e. Something like "doAction( () -> myfunction() );". The lambda will often end up null after a recompile. Weirdly extracting this out into a separate variable ala "final Runnable action = () -> myfunction(); doAction(action);" seems to "fix" this or at least reduce the frequency of this bug so much that we don't notice. We have never invested the time to track down the exact cause of this. HTH On Tue, Dec 5, 2017 at 9:37 PM, Jens <[email protected]> wrote: > GWT SuperDevMode only compiles changes (and its dependencies) but sometimes > it might miss a change which can result in broken code. As you said the only > workaround is to force a change to the affected method or clean SDM cache > and rebuild the whole app (click the small clean button on the SDM UI at > localhost:9876). > > Of course it is a bug but without being able to reproduce it, I guess it is > tough to find and fix. > > -- J. > > -- > 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. -- Cheers, Peter Donald -- 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.
