This is why, under Eclispe, I would use the RunJettyRun plugin, which exe uses Jetty directly off your workspace files and compiled classes. That works perfectly.
Delegating out to Gradle means that, at best, when Eclipse compiles files, they are copied to the directory served by Jetty, which only knows to redeploy the application. On Thursday, November 1, 2012, Andy Pahne wrote: > > Hi, > > I did all of that except turning off hot code swapping. I just did not > find, > where to turn that off in Eclipse. I found "Configuration - Java - Debug", > where I can adjust what happens if hot code swap fails or isn't available, > but I did not find, how to turn it off. > > After working through the list, a change in template files or class files > is > recognized automatically and the context is restarted as well. But that is > not quite what I am expecting, because that still takes very long, given > that I am dealing with a Spring/Hibernate application. And I am sure, that > wasn't the case, when I was working with T5 in previous projects. My > previous experience was, that a change was picked up without a full context > restart. > > Andy > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/template-class-reloading-and-gradle-s-jetty-run-tp5717491p5717527.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org<javascript:;> > For additional commands, e-mail: users-h...@tapestry.apache.org<javascript:;> > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
