I use Jetty 5 Plus run in Eclipse via the JettyLauncher plugin. I occasionally use the Debug As in Eclipse, but most of the time I just Run and use the great T5 error reporting.
When using Debug As, Eclipse will often grumble that it can't replace the (running) code. I frequently find that I can keep going and everything is OK, but a restart is advisable and usually fast. I should also comment that what I find when I use Debug As is usually stuff that would have easily been caught had I written the unit test that I should have started with. Jonathan > -----Original Message----- > From: limonn [mailto:[EMAIL PROTECTED] > Sent: Friday, August 22, 2008 09:19 > To: users@tapestry.apache.org > Subject: t5: debugging with jetty > > > How do you guys debug using jetty, any guidance steps for that ? > > How that affects the feature of no need to restart jetty for changes to > show > ? > > Thank s in advance > -- > View this message in context: http://www.nabble.com/t5%3A-debugging-with- > jetty-tp19107119p19107119.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
