On Friday, March 11, 2011 12:48:13 PM UTC+1, Filipe Sousa wrote: > > On Friday, March 11, 2011 9:15:42 AM UTC, Thomas Broyer wrote: >> >> In my setup, I run a "mvn package" or "mvn war:exploded" once, so that all >> dependencies are copied to target/mywebapp-0.0.1-SNAPSHOT/WEB-INF/lib and >> then run Jetty. It works very well, given that my dependencies do not change >> that much. In the event that they change, I could in theory (untested) just >> run "mvn war:exploded" (or copy the JARs manually) without restarting Jetty, >> redeploying the webapp would be enough (as I understand it, you would have >> to restart your JettyDevServer). >> > >> > I'm not restarting JettyDevServer. My workflow is: change code on the > server side, press F1 key (/bin/touch context.xml) to hot deploy in less > than a second, and finally, refresh the browser. I don't create any WAR, > except when I want to use on a production server. >
When you didn't change your dependencies, yes; but if you changed them (added a JAR, upgraded to a new version, etc.), you'd have to restart JettyDevServer so it runs with the updated classpath. It's a really a minor nit though (couldn't even write "annoyance" here ;-) ), as Jetty is not only fast at redeploying but also fast at startup! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
