You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting in GWT 2.11 (see #9863 and #9866) a new dev mode server implementation was introduced - com.google.gwt.dev.shell.StaticResourceServer. At the same time, the JettyLauncher implementation was deprecated, and logs a warning to the console when used.
This ticket proposes that in GWT 2.13 the default be changed to StaticResourceServer, with the JettyLauncher left for at least one more version before being removed.
As an alternative, we could remove the default server entirely and change to -noserver by default, so that any user specifying -server needs to also pick the server implementation they want to use.
The text was updated successfully, but these errors were encountered:
I can see JettyLauncher etc. disappearing eventually, primarily in favor of external server wiring but also in relation to maintenance headaches and related struggles.
Starting in GWT 2.11 (see #9863 and #9866) a new dev mode server implementation was introduced -
com.google.gwt.dev.shell.StaticResourceServer
. At the same time, the JettyLauncher implementation was deprecated, and logs a warning to the console when used.This ticket proposes that in GWT 2.13 the default be changed to StaticResourceServer, with the JettyLauncher left for at least one more version before being removed.
As an alternative, we could remove the default server entirely and change to
-noserver
by default, so that any user specifying-server
needs to also pick the server implementation they want to use.The text was updated successfully, but these errors were encountered: