I use IntelliJ Ultimate and use the bundled Jetty integration plugin of IntelliJ. This is not the Jetty Runner plugin you are using. The bundled Jetty integration plugin lets you start a local Jetty just fine via a run configuration and lets you configure *.war or exploded war files to deploy. The run configuration as a "before launch" action that actually builds the war file using Gradle.
In your case it sounds like you have gwt-dev.jar on classpath and that Jetty Runner plugin uses the same classpath. Thus it can happen that jetty 9.2 from gwt-dev.jar might get started. As an alternative (if you only have IntelliJ Community Edition) you could just download jetty and start it locally on your dev machine without any IntelliJ involved. Then use IntelliJ or whatever to produce a war file into the jetty/webapps folder. You could also create a symlink or use a script to copy your compile output into that webapps folder. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f8c60f86-6cda-4389-b528-131f324af44f%40googlegroups.com.
