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
I have noticed temporary files and folders created during "DevMode" and "codeserver" execution, which are never deleted because there is no way to exit the running process gracefully.
Some of the folders seem to be generated by "codeserver" , some others by the GWT compiler , some others by Jetty, etc.
There is also possibility for more temporary folders being be created by custom DevMode launchers, leading to even greater waste of space.
GWT is expected to be cleaning these folders on JVM exit, if it does not already.
Theoretically, GWT Plugin should able to send a graceful termination signal to the running DevMode process.
I have noticed temporary files and folders created during "DevMode" and "codeserver" execution, which are never deleted because there is no way to exit the running process gracefully.
Some of the folders seem to be generated by "codeserver" , some others by the GWT compiler , some others by Jetty, etc.
There is also possibility for more temporary folders being be created by custom DevMode launchers, leading to even greater waste of space.
GWT is expected to be cleaning these folders on JVM exit, if it does not already.
Theoretically, GWT Plugin should able to send a graceful termination signal to the running DevMode process.
Would such a feature be desirable ?
see also gwtproject/gwt#10109
The text was updated successfully, but these errors were encountered: