SuperDev Mode Java files are not sent to the browser

[ustakraharez]

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!

[Paul Stockley]

One you bring the dev tools up hit refresh on the page.

[emurmur]

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

[Paul Stockley]

I think the issue could be related to this:

https://gwt-review.googlesource.com/#/c/1300/1

[emurmur]

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

[emurmur]

Well, I'm not sure how to rollback to Chrome 23.  I tried updating my GWT plugin and SDK to latest (SDK 2.5.0 from 12/12/12 I think), but no dice.  Now I'm really stuck.  I depend on code server and chrome dev tools.  Code server was supposed to be the way to avoid issues with browser upgrades.  Does anyone from the GWT team have a suggestion?  Is anyone out there successfully using Chrome 24/25 and Code Server and Source Maps?  Thanks for your help.

Ed

[Thomas Broyer]

We'll release 2.5.1 in the coming weeks, and it will have the fix. If you really need it, then either patch your GWT 2.5.0 or build GWT from trunk (we'll cut 2.5.1 from trunk)

[emurmur]

Looks like it is fixed in SDK 2.5.1, which is not yet released; http://code.google.com/p/google-web-toolkit/issues/detail?id=7725&q=sourcemaps&colspec=ID%20Type%20Status%20Owner%20Milestone%20Summary%20Stars

There is no 2.5.1RC available yet.  Does anyone know when that may appear?  Anyone have a process for rolling back to Chrome 23?

Ed

[emurmur]

I think we posted on top of each other.  Thanks for the timetable on 2.5.1.  I have not been building from source, so that is a big time-suck for me to setup and then patch.  I'll try to rollback to Chrome 23 first.  Thanks again.

Ed

[ustakraharez]

Dear All,

For me, if is a big help already, that I'm not completely crazy :-)

Thanks a lot, and waiting for the fixed release.

Best:

Gabor

[emurmur]

I built trunk (you guys make this easy, thanks).  I used the sdk that I built from trunk (gwt0.0.0.0) and switched my project to this new sdk.  That worked (after I fixed the path to gwt-codeserver.jar in my run configuration to point to the new codeserver).   Thanks for your help.

Ed

On Monday, January 14, 2013 6:23:24 PM UTC-8, Thomas Broyer wrote: