Friday, May 9, 2014

GWT Gradle plugin: changing port? Tomcat vs Jetty?

I'm trying out Gradle, the gwt-gradle-plugin, and Super Dev Mode. I've got the plugin (https://github.com/steffenschaefer/gwt-gradle-plugin) and am trying to run the super-dev-mode example. Since Tomcat is already running on my workstation, I want to change the Jetty port from 8080 to 8888. However although I set "cargo { port = 8888...", I still get

    :jettyDraftWar
    failed SelectChannelConnector@0.0.0.0:8080: java.net.BindException: Address already in use

when I run `gradle jettyDraftWar`. If I run `gradle cargoRunLocal`, things are fine and I can run my app, but I suspect that's not doing everything the gwt-gradle-plugin intends, and I want to get off on the right foot (vs my initial bumbling around with Maven and SDM).

Is this a bug or should I be setting httpPort somewhere? I've tried several places. Jetty opens 8888 but the app cannot be found.

Also, I can get my app running with Tomcat using tomcatRunWar (with alternate port and ajp.port), but I'm not finding the magic to do this via the gwt-gradle-plugin. Can anyone help?

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment