Thank you. I appreciate the time that you and others put into this group
(and GWT in general).
It took some more bumbling around, but I found it worked with two additions
(highlighted below):
...
cargo {
containerId = 'jetty9x'
port = 8888
deployable {
file = tasks.draftWar.archivePath
context = 'app'
}
local {
installer {
installUrl =
file("$projectDir/etc/jetty-distribution-9.0.5.v20130815.zip").toURI()
downloadDir = file("$buildDir/download")
extractDir = file("$buildDir/extract")
}
}
}
task jettyDraftWar(type: JettyRunWar) {
dependsOn draftWar
dependsOn.remove('war')
webApp=draftWar.archivePath
*httpPort = 8888*
* contextPath = 'app'*
}
...
This being Gradle, there are probably three other ways I could have done
it, but it took me enough tries to find this one. :-/
That accomplished, if it makes no difference from the server side, I may
just stick with Cargo. We'll see when it comes to Eclipse and servlet
debugging.
I must say that while I can see how useful Gradle might be--assembling a
GWT app, Javadocs, server apps, etc. can be difficult--learning Gradle is
no small task. After a day walking through the exercises in *Maven by
Example <http://books.sonatype.com/mvnex-book/reference/public-book.html>* I
understood it well enough to start converting my project, from base
libraries on through to the final distro. I've been banging away at the Gradle
User's Guide <http://www.gradle.org/docs/current/userguide/userguide.html>and
Ikkink's Gradle
Effective Implementation
Guide<http://shop.oreilly.com/product/9781849518109.do>for a while now and
still feel overwhelmed.
Coming soon--mgwt 2.0, Elemental, Java8 Lambdas, GWT 3.0... Some day I
really hope to have the time to read fiction again.
On Friday, May 9, 2014 5:56:15 PM UTC-4, Jens wrote:
>
> If you run jettyDraftWar which is probably of type JettyRunWar you must
> configure the jetty plugin. If you run cargo then you must configure jetty
> through the cargo plugin.
>
> For the cargo plugin you configure the port using cargo { port = 8888 ...
> } and for the jetty plugin you configure the port using "jettyRun.httpPort
> = 8888" or "jettyRun { httpPort = 8888 }".
>
> In general you are not forced to use both Jetty plugin and cargo plugin. I
> guess the SDM example just wants to show that both is possible. Also I
> think that the gwt-gradle-plugin does no additional magic behind the scenes
> when running jetty or tomcat or anything else to serve your app. The
> gwt-gradle-plugin only starts SDM and thats all.
>
> How you serve your app and which plugin you choose to do so is up to you.
>
>
>
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
