Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change default dev mode server to static implementation #10057

Open
niloc132 opened this issue Dec 12, 2024 · 1 comment
Open

Change default dev mode server to static implementation #10057

niloc132 opened this issue Dec 12, 2024 · 1 comment
Milestone

Comments

@niloc132
Copy link
Member

niloc132 commented Dec 12, 2024

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.

@eliasbalasis
Copy link

eliasbalasis commented Dec 12, 2024

I can see JettyLauncher etc. disappearing eventually, primarily in favor of external server wiring but also in relation to maintenance headaches and related struggles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants