On Friday, March 11, 2011 3:02:27 PM UTC, Thomas Broyer wrote: > > >> 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! >
In that case yes, but the JARs are almost never updated. If I had JARs that needed to be updated often, they would go into WEB-INF/lib. Jetty is amazingly fast. I hope it stays that way for a long time. The only problem is that now I don't have time for coffee between deploys. -- 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.
