Hi, I do not know about version 2.8, but for 2.6 we did next: - put value "PRETTY" in the pom.xml for gwt plugin - put next loggin settings in the application gwt config file
<inherits name="com.google.gwt.logging.Logging"/> <set-property name="gwt.logging.logLevel" value="FINEST"/> <set-property name="gwt.logging.consoleHandler" value="ENABLED"/> <set-property name="gwt.logging.simpleRemoteHandler" value="DISABLED" /> <set-property name="gwt.logging.popupHandler" value="DISABLED" /> <set-property name="compiler.stackMode" value="emulated" /> <set-configuration-property name="compiler.emulatedStack.recordLineNumbers" value="true"/> <set-configuration-property name="compiler.emulatedStack.recordFileNames" value="true"/> as result we had a proper class names and line numbers in the stack-trace massages понеділок, 5 листопада 2018 р. 19:59:15 UTC+1 користувач brad написав: > > Hi, > > Two issues that often frustrate me with GWT deobfuscated stack traces: > a) The stack trace is deobfuscated, but the error message is not, so you > get something like "com.google.gwt.core.client.JavaScriptException: > (TypeError) : Cannot read property 'a' of undefined". > b) The stack trace refers to methods headers, rather than specific lines. > > In many cases, neither of these is a big deal, but if the message is > obscure and the method in question is long it can make debugging difficult. > Is there anything that can be done to work around this (compiler > properties, etc.). This is particularly for debugging a deployed > application, not locally using super dev mode. > > Thanks, > Brad > -- 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.
