It is an IDE/jetty:run problem because they must work together. Jetty is scanning for file changes - but the IDE must actually save files to the location being scanned. After following Gilberto's link and changing the IDEs "Compile on Save" parameter, Jetty restarts now when I make changes to class files.
Unfortunately, the scanning path doesn't seem to pick up the html files in src/main/webapp. It only seems to scan the files in target/* ... so, we're close. The class file changes get picked up but changes to the htm files do not yet cause Jetty to restart (and consequently, I continue to see the old file in the browser). Thanks for the suggestions. -- View this message in context: http://click.1134972.n2.nabble.com/Optimal-Development-Cycle-tp5457365p5459337.html Sent from the click-user mailing list archive at Nabble.com.
