Jetty is a fine choice, but Tomcat works just the same for live class reloading: http://tynamo.org/Developing+with+Tomcat+and+Eclipse
Kalle On Fri, Nov 26, 2010 at 8:31 AM, Richard Hill <r...@su3analytics.com> wrote: > > 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
