Thanks Jen. Using your class, the method names of the exceptions are still obfuscated, but at least it shows the class name and line number, which can be clicked to get to the source.
While we're on the topic, is there a similar workaround for debugging (setting break points, etc)? If a breakpoint is set in Chrome, the scope variables all have obfuscated names. Is there a way to debug from within the IDE? On Fri, Feb 13, 2015 at 8:35 PM, Jens <[email protected]> wrote: > > Is there a workaround for getting the stacktraces to show up without being >> obfuscated? >> > > If you use Chrome 40 and use the UncaughtExceptionHandler I linked in the > issue (comment #4) then you do not need anything regarding stack traces in > your module xml. Any exception you do not catch will be logged nicely to > browser console with clickable links to your source mapped Java file. > > -- J. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google Web Toolkit" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-web-toolkit/He7Q5NBIQZU/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
