Of course, having mucked around for over an hour, finally caved in and decided to ask the mailing list, I immediately found the problem:
You need to include your web project in the Jetty classpath, not just project dependencies. (This was T5.1 btw) Thanks all -----Original Message----- From: Richard Hill <r...@su3analytics.com> Reply-to: r...@su3analytics.com To: Tapestry users <users@tapestry.apache.org> Subject: Jetty and live class re-loading (again) Date: Fri, 26 Nov 2010 16:31:05 +0000 Hi All, I today have attempted switching from Tomcat to Jetty in order to take advantage of live class reloading. However sadly live reloading is not working for me at the moment. I'm not using run jetty run or maven, I downloaded and unpacked jetty myself, and installed it in eclipse using the Jetty Server Adaptor from webtide. In eclipse I have "Build Automatically" selected. Jetty is configured to "Automatically republish when resources change". And my jetty VM args includes: -Dorg.mortbay.jetty.webapp.parentLoaderPriority=true The really annoying issue is that even a static asset change such as .css modification requires what seems to be a full rebuild and deploy, which takes a good 10 seconds. Is there some hidden config option I am overlooking? Any gotchas that people have experienced with getting this working? Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
