Thanks, I just ran the code server. The main reason I did this is because Idea runs both the code server and Jetty Server together and passes the same class path to both. Our app has a lot of server dependencies and not too many client specific ones. By breaking them up I was able to tailor the class paths and dramatically speed up the code server. Plus now we can restart the jetty server and not be forced to reload the code server. Although this isn't as big a deal for us because we use JRebel.
On Sunday, August 21, 2016 at 9:16:27 AM UTC-4, Jens wrote: > > You can also just launch CodeServer.main() unless you somehow need the > embedded Jetty server launched by legacy DevMode class for your server side > code (although IMHO its better to have CodeServer and Servlet container in > two different processes so you can relaunch them separately). CodeServer > does not have any Swing UI. > > -- J. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/03e86b3a-e55b-47ee-a7ea-07929dde6108%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
