I created this issue with my concern about not using embebed jetty (https://github.com/gwtproject/gwt/issues/9437). For me the main problem is that the codeserver do not uses the auto-recompile.nocache.js, so I use the devmode but the embebed jetty is just to open the client side app, non server-side classes or libs are actually used in devmode. IMO Now, using devmode with client-side-only on standalone client or CORS compatible server is a quite confortable workflow.
On Wednesday, March 1, 2017 at 11:54:37 PM UTC+1, Brandon Donnelson wrote: > > I'd like to discontinue enhancements with anything related to DevMode and > focus on all development, fixes, enhancements around the Code Server > launcher only. Not that it needs to be fixed, but with any development > going forward, I'd push folks into using the Code Server to launch GWT Dev > Mode (super development mode). There are so many edge cases with using the > embedded jetty or Dev Mode launcher, it's finally got to me. I think things > need to be made simpler and focus on the modern debugging should be out > front. > > I may be in a mood, because there is a lot of code to maintain around > this. So I'm asking if this seems to drastic at this point? > > Thanks, > Brandon > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/456d87cb-47ba-4792-a0e4-e2ecf4faebb3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
