That makes sense. I just uninstalled Chrome 25 and installed latest Chrome (24) and still have the issue. I probably need to back up to 23, which is what I had this morning when everything worked. Thanks for finding that.
Ed On Monday, January 14, 2013 5:16:13 PM UTC-8, Paul Stockley wrote: > > I think the issue could be related to this: > > https://gwt-review.googlesource.com/#/c/1300/1 > > On Monday, January 14, 2013 7:46:26 PM UTC-5, emurmur wrote: >> >> Unfortunately, I'm just now experiencing the same thing. It started >> happening immediately after I update to Chrome 25. It's not clear yet that >> Chrome 25 is the issue. Here is what I did; >> >> 1) I was in Chrome 23, happily using code server for compiling and source >> maps and chrome dev tools for debuggging. >> 2) I wanted to try the new speech features in Chrome 25, so installed the >> beta, the restarted chrome (while eclipse and code server were running). >> 3) I opened up the html file again. I made some changed to my source and >> compiled it in chrome using the code server bookmark. It compiled >> correctly, but only javascript source was available. The compiler output >> shows the source maps are enabled. I checked the chrome dev tools setting >> and they indicate source maps are still enabled in chrome. >> 4) I then did a bunch of stuff in various combinations,refreshing the >> page, clearing the cache, restarting chrome, restarting code server, doing >> full GWT compile then starting code servers, etc. Still no source maps. >> >> So, I'm not sure if it was the upgrading of the browser, or restarting >> the browser while code server was running. I'll continue to work on this >> and let you know what I find. If you figure this out, please reply and let >> me know what you found. Thanks much. >> >> Ed >> >> >> On Sunday, January 13, 2013 1:06:24 AM UTC-8, ustakraharez wrote: >>> >>> Dear All, >>> >>> I have a strange problem with SuperDev mode. Sometimes it sends the java >>> files to the browser, sometimes (and sadly more times :-)) it don't. >>> >>> - SuperDev mode run configuration set, and working. >>> - Superdev mode url working >>> - Bookmarks are working, and when I hit Dev Mode On, compiling working >>> (console logged in Eclipse) >>> - But here, nothing happens. When I follow the modulename url from the >>> browser, I can see the compiled source files, but when I open Chrome Web >>> tools, on Sources (and Profiling) tabs only the cache.js can be seen. >>> Source Maps enabled in Chrome of course. >>> >>> I also aware, that if source maps working properly, the *[WARN] : >>> Source maps sent for module : moduleName* can be seen in Eclipse logs. >>> I only don't understand, what is the reason why it is sometimes working and >>> more times not. >>> >>> Thanks a lot for your help! >>> >> -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/il6xSyKpqBQJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
