Thanks cool, this way it works just fine, I also had to symlink my java sources so the browser could access them, you can do this by creating a symlink to you com (org or whatever package you use as base) in you war/<project-name> folder (where the cache.htmls are generated and where you copy source maps to). It would probably be a lot better to have a servlet that can handle fetching the sources and also a modified linker that adds the sourceMappingURL to the generated JS (I guess this gets more complicated when code splitting is in play).
Honza On Mon, Apr 2, 2012 at 09:27, Dan Cojocar <dan.cojo...@gmail.com> wrote: > Yes, some bits are still missing, but using trunk and following the > instructions from here: > http://code.google.com/p/google-web-toolkit/wiki/SourceMaps (with few > additional steps, mentioned in the comments) I was able to debug the Mail > application, using the java sources in Development tools. > > On Mon, Apr 2, 2012 at 9:45 AM, Honza Rameš <rame...@gmail.com> wrote: > >> Yep, I'm using trunk but I'm not sure that the source map support is >> fully functional even in trunk though it gets generated. I tried both >> canary and dev channels of Chrome (I think even Googlers won't use anything >> special since canary is almost daily build but we cannot be sure ;-) ) >> >> Honza >> >> >> On Sun, Apr 1, 2012 at 18:34, Gal Dolber <gal.dol...@gmail.com> wrote: >> >>> oh, my mistake, it seems SourceMap is there.. are you using trunk? >>> >>> >>> On Sun, Apr 1, 2012 at 12:31 PM, Gal Dolber <gal.dol...@gmail.com>wrote: >>> >>>> got exited for a minute... its not there yet, I'm checking out trunk >>>> everyday hoping to see SuperDraftMode and SourceMap commited >>>> >>>> >>>> On Sun, Apr 1, 2012 at 7:20 AM, Andrea Boscolo <andrew...@gmail.com>wrote: >>>> >>>>> Are you sure the whole machinery is already available in the public >>>>> (trunk) repo? I thought it's not. >>>>> >>>>> https://plus.google.com/u/1/110412141990454266397/posts/Nvr6Se6eAPh >>>>> >>>>> >>>>> On Sunday, April 1, 2012 12:16:05 PM UTC+2, Honza Rames wrote: >>>>>> >>>>>> Hi everyone, >>>>>> I tried to compile my GWT app with source maps support (as explained >>>>>> here http://stackoverflow.com/**questions/9804492/how-to-try-** >>>>>> sourcemaps-with-gwt<http://stackoverflow.com/questions/9804492/how-to-try-sourcemaps-with-gwt>) >>>>>> and it failed at first (some json stuff was missing) so I added it to my >>>>>> project's class path then it compiled OK and I can see the source maps >>>>>> generated in WEB-INF/deploy/<project>/**symbolMaps. I should also >>>>>> note that I'm using custom build of GWT from trunk. I enabled source maps >>>>>> support in Chrome's Developer tools setting panel but I the source maps >>>>>> doesn't seem to work. I'm launching the app through jetty but not in dev >>>>>> mode (obviously ;-) ) I compiled the project in obfuscated mode as >>>>>> standard >>>>>> compile (no draft or anything like that). Do I have to use another >>>>>> version >>>>>> of Chrome? Does anyone tried this as well and succeeded? >>>>>> >>>>>> Honza >>>>>> >>>>> -- >>>>> 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/-/hcGUk2-d124J. >>>>> >>>>> 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. >>>>> >>>> >>>> >>>> >>>> -- >>>> Guit: Elegant, beautiful, modular and *production ready* gwt >>>> applications. >>>> >>>> http://code.google.com/p/guit/ >>>> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Guit: Elegant, beautiful, modular and *production ready* gwt >>> applications. >>> >>> http://code.google.com/p/guit/ >>> >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google Web Toolkit" group. >>> 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. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> 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. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > 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. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
