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
Is the Maven goal for DevMode working with GWT 2.9.0 , or is it suffering from the known GWT 2.9.x build classpath symptoms as the ones mentioned under (gwtproject/gwt#9720) and the referenced issues
The text was updated successfully, but these errors were encountered:
But to answer your question, given that this plugin only runs GWT in forked JVMs, without any modification or even classpath/classloader tricks, then yes it suffers from the same limitations.
The advice above applies to GWT generally, whether run through this plugin or anything else (Ant, Gradle, your IDE, etc.)
I was referring to "Super DevMode" not standard "DevMode", which I am primarily using via "Google Plugin for Eclipse" but I have to agree that even though "codeserver" is not as simple it at least bypasses the Jetty runtime classpath issues.
I haven't tried this, but I wonder:
Is the Maven goal for DevMode working with GWT 2.9.0 , or is it suffering from the known GWT 2.9.x build classpath symptoms as the ones mentioned under (gwtproject/gwt#9720) and the referenced issues
The text was updated successfully, but these errors were encountered: