Development Mode - Jetty - Realm - Redirecting to 403 - Forbidden page - GWT - 2.8.0

2018-01-16 Thread Srini R
Is this right place to discuss about my issue ? Just raised in Github. Please help. Its urgent. Thanks. https://github.com/gwtproject/gwt/issues/9589 -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop

Re: Chrome debug crash with super devmode

2018-01-16 Thread Thomas Broyer
IIRC, some (many?) people aren't using source maps at all, using -style PRETTY to get readable JS code. That might be an acceptable workaround in your case. On Tuesday, January 16, 2018 at 10:49:16 AM UTC+1, Joffrey Diebold wrote: > > Hi, > I can't use super devmode with Chrome for debugging

Re: GWT 2.8.2 release

2018-01-16 Thread Thomas Broyer
On Tuesday, January 16, 2018 at 10:47:51 AM UTC+1, Jörg Pfründer wrote: > > Dear GWT-Team, > > thank you that you have done a great job in the past. We have a large > codebase strongly relying on GWT. However the last release has caused big > pain to me: > > I have tried to update from version

Chrome debug crash with super devmode

2018-01-16 Thread Joffrey Diebold
Hi, I can't use super devmode with Chrome for debugging because when the source panel of the developer tools is opened, then the Chrome process (not the whole Chrome) crashes. The cause seems to be the request of both files sourceMap.json and symbolMap. The last message logged in the console

Re: GWT 2.8.2 release

2018-01-16 Thread 'Jörg Pfründer' via GWT Users
Dear GWT-Team, thank you that you have done a great job in the past. We have a large codebase strongly relying on GWT. However the last release has caused big pain to me: I have tried to update from version 2.7 to 2.8.2 to get rid of my dirty bugfix hacks for chrome 61 positioning. But I was