Saturday, September 12, 2015

Re: Basic SuperDevCompiler + SuperDevModeUI Library

Using intellij GWT run configuration with Tomcat7

"C:\Program Files\Java\jdk1.7.0_65\bin\java" -Xms2048m -Xmx2048m -XX:MaxPermSize=1024m -Didea.launcher.port=7536 "-Didea.launcher.bin.path=E:\Jetbrains\IntelliJ IDEA 14.1.4\bin" -Dfile.encoding=windows-1252 -classpath "C:\Users\Ben\.m2\repository\com\google\gwt\gwt-codeserver\2.7.0\gwt-codeserver-2.7.0.jar;
..."lots of jars"...
com.intellij.rt.execution.application.AppMain -superDevMode -war C:\Users\Ben\.IntelliJIdea14\system\gwt\xxx-project.e34dc554\xxx.dcb6c866\run\www -noserver -remoteUI 7903:IntelliJIdea -startupUrl

Runing CodeServer with parameters: [-noprecompile, -port, 9876, -sourceLevel, 1.7, -bindAddress,, -launcherDir, C:\Users\Ben\.IntelliJIdea14\system\gwt\xxx.e34dc554\xxx.dcb6c866\run\www, -logLevel, INFO,]
Super Dev Mode starting up
   workDir: C:\Users\Ben\AppData\Local\Temp\gwt-codeserver-4027014467612992043.tmp
   Loading Java files in
Linking modules
   Bootstrap link for command-line module ''

On Sunday, September 13, 2015 at 1:10:30 AM UTC+12, Jens wrote:
Either launch (other parameters omitted)

DevMode -noserver -war /path/to/exploded_war


CodeServer -launcherDir /path/to/exploded_war

with /path/to/exploded_war being your build tool's output war directory or your GWT-Project/war folder. At work we do this for ages because we always use the exact same servlet container as we use in production. So we literally never used GWT's bundled jetty server.

What problems did you encounter? When coming from GWT 2.6 classic DevMode it should actually just work without any changes to your configuration.

-- 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
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment