Thanks for the suggestions. In this case, I was able to navigate to the project's properties and find Build | Compile where I changed the "Compile on Save" option to "For both application and test execution". That seemed to do it. Jetty now restarts automatically on changes to class and templates.
This last comment peaked my interest - session preservation would be nice - ie: I assume that hot deploys are "in place" and the server doesn't actually restart. Hmmmm.... -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-and-Netbeans-tp2337063p2337510.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
