You only need to "gwt compile" once, then just run DevMode. Ideally, you'd point DevMode's -war at the location Jetty loads your webapp (so, deploy an exploded WAR, or point -war to the location Jetty exploded the WAR in the temp folder) so that all the static files it generates (ExternalTextResource; other resources when not inlined for whichever reason, ImageBundle if you still use them; and GWT-RPC serialization policies) can be found by Jetty / your webapp.
In many situations, when working on client-only code (UI code, mostly), I just run DevMode in -noserver mode with -startupUrl pointing at our test server (where our CI server deploys the app). Otherwise, we use a local Jetty server and configure it to load the webapp right from our Maven's target/ folders; that way redeploying is just a matter of re-compiling the Java classes (done automatically by Eclipse anyway, but otherwise "mvn package -Dgwt.compiler.skip" does the job without recompiling the GWT client-side code), and with DevMode you never need to redeploy the client-side code. On Tuesday, November 19, 2013 9:39:29 PM UTC+1, jay wrote: > > We have some requirements which have forced us to run our own Jetty > server. This means we're debugging with the --noserver flag. The problem > with this is the amount of time it takes to do a command line build (and > deploy) and then run the debugger. And, of course, if your command line > compile doesn't include the right permutation, you get to do it all over > again. > > My question is if someone can point us at how we can use our Jetty > process, but hook up the GWT dev mode "magic" so we can just fire up the > debugger and go. > > Thanks, > > jay > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
