Hm, I hadn't thought about making the CodeServer the default yet. I've been helping folks convert to super dev mode every chance I get so my feeling is that keeping the legacy the default method that starts up with SDM probably is the way to go on for a bit longer. I've got to be careful I don't bite off more than I can chew so my goal is to get the CodeServer launcher running swimmingly. That said, I'm afraid of upsetting the applecart too much by doing any big changes. Since the CodeServer launcher came later, I've been keeping it as a new launcher. I think it's effective to use with custom integrated and external server runtimes. The integrated jetty server usually doesn't fit most enterprises production structures so it causes all kinds of dev strategy workarounds to make things work well. And using DevMode with -noserver works great for most things but the proxy of the arguments from DevMode doesn't work for every situation like CodeServer does.
Although there is another branch for the GWT Eclipse plugin that I'm working on which will be the new and improved version. This I think might be the ticket to change the feature here. In fact I like the idea for this branch. I'm having to separate out the Google cloud tools to make way for combining up with the cooler stuff coming from the Google Cloud Plugin. Good idea, thanks. -Brandon On Thu, Aug 25, 2016 at 5:24 PM Jens <jens.nehlme...@gmail.com> wrote: > I guess the future is CodeServer + optional external servlet container. > > So IMHO it would be more straight forward to just have "GWT Web > Application" which always launches CodeServer.main() directly and not > through DevMode.main(). Within this run configuration you can optionally > choose to automatically launch an external servlet container as well, e.g. > through Eclipse WTP or by running a second run configuration like a maven > goal / gradle task or a terminal command. > > => normal GWT icon > > > If you want to support the legacy guys there would be "GWT Web Application > (legacy)" which would launch classic DevMode > > => GWT icon with some standard Eclipse server icon > > > -- J. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "GWT Contributors" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-web-toolkit-contributors/WGLtekU5U5U/unsubscribe > . > To unsubscribe from this group and all its topics, 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/6e8f5a16-6d20-41b2-bb99-bb3964cbfda7%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/6e8f5a16-6d20-41b2-bb99-bb3964cbfda7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPnsdHQQcbPw0yxGUwGVEGa2bDN6Q6R6Yo7SMbogc0h_eNVNWQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
