Monday, October 27, 2014

Re: CodeServer vs DevMode for 2.7.0

I think you need to add gwt-codeserver.jar to the classpath; but you should have some logs if something fails.

IIUC this will be done automatically with the next release of the Google Plugin for Eclipse.

On Monday, October 27, 2014 4:59:42 PM UTC+1, funkforce wrote:

I am sorry but I cant understand what you say. Can you please show an example of a configuartion that works? I just download 2.7beta and even my old configuration from 2.6 doesn't work anymore with an external appserver. Heres are my arguments:

-startupUrl -war /home/icomprice/workspace/icpGWT/war -remoteUI "${gwt_remote_ui_server_port}:${unique_id}" -logLevel INFO -noserver -codeServerPort 9997 icp.ui.cpGWT.

I tried to add -superDevMode but with no luck.

Thanks in advance.

On Monday, October 27, 2014 3:45:42 PM UTC+1, Thomas Broyer wrote:

On Monday, October 27, 2014 1:19:16 PM UTC+1, Filipe Sousa wrote:

With gwt 2.7.0-beta1 should we use or with -superDevMode?

DevMode defaults to -superDevMode now.
Which one you use depends on your needs. If the embedded server of DevMode is OK for you, then use DevMode. Otherwise, then you'd better use CodeServer (possibly with the new -launcherDir arg to get the same behavior as with DevMode) than DevMode with -noserver.
We could almost say that "CodeServer is the new 'DevMode -noserver'" (then you use -launcherDir when everything's in your control –and the launcherDir is served by your server– and you don't if you want/need to use the bookmarklets, e.g. when debugging on a shared "testing" or "staging" server)

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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