Maybe try out the new GWT Eclipse Plugin, which (AFAICT) bundles everything 

On Monday, October 17, 2016 at 12:48:38 AM UTC+2, Namline wrote:
> Jens,
> Actually, I took your advice and managed to set break points in Chrome's 
> Developer tool (in Source tab, under sourcemap folder where the Java 
> classes are) and debug from there (not that anything made sense with all 
> the generated JavaScripts).
> I also tried SDBG which more or less does the same thing but in the 
> Eclipse as a plugin. I just followed the video on SDBG site 
> <>and got it to work. What was confusing about it 
> was to run debugging in SuperDevMode first, then rerun the Eclipse Debug 
> As, but this time Launch Chrome from Debug Configuration. It actually 
> spawns two (2) debugging sessions from the looks of it: one for Web 
> Application (code server) and the other for Launch Chrome. Thanks for the 
> recommendation.
> On Sunday, October 16, 2016 at 3:46:59 PM UTC-4, Jens wrote:
>> SuperDevMode compiles your Java source transparently to JavaScript, it 
>> never executes your Java source code directly in a JVM. So Java break 
>> points in your GWT app will never work.
>> That means with SuperDevMode you can only debug your code using the 
>> browser, as thats the one who actually executes the final JS code. You can 
>> either set break points in your browsers dev tools or install the Eclipse 
>> plugin "SDBG" which allows you to set break points in your IDE which are 
>> then synchronized to the browser.
>> -- 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 post to this group, send email to
Visit this group at
For more options, visit

Reply via email to