>
>
>
> ...
>
> ...
>
>
> Is that correct?
>
Yes thats correct. With the above you should see source maps applied to
stack traces when using Chrome. But you do not have to set
compiler.stackMode explicitly to native as native is the default. You can
see this i
Thanks Jens,
I do see the Java sources in Chrome and can debug. Fort for the settings, I
suppose you mean :
...
...
Is that correct? And can you please point me to a documentation link for
it...
Thanks!
On Friday, April 22, 2016 at 3:52:58 AM UTC-7, Jens wrote
Do you see source maps (and thus your java files) in your Chrome dev tools
under the "sources" tab? If not, then Chrome has not loaded source maps for
any reason.
Also if your have inherited Logging.gwt.xml then the property
compiler.stackMode must be set to native in order to see stack traces
Hi all,
I often get stack traces like the one below at run-time, which are not
helpful at all. Am I missing some compiler switch in GWT 2.8 or what? I do
have source maps enabled in Chrome.
com.google.gwt.core.client.JavaScriptException: (TypeError) :
this.$$outer_0_27_g$.lambda$0_11_g$ is not
