There are perfectly good Tomcat launchers for Eclipse as well that don't use the cumbersome WTP infrastructure that copies files around (causing these issues and bad performance). http://merve.sourceforge.net/ works exactly like Jetty launcher (but hasn't been updated for a while) and Sysdeo's Tomcat plugin http://www.eclipsetotale.com/tomcatPlugin.html that offers more features.
Kalle On Wed, Mar 18, 2009 at 10:07 AM, Peter Stavrinides < p.stavrini...@albourne.com> wrote: > Tomcat in the eclipse WTP can be very sensitive, I spent hours fiddling > with it, so if you can use Jetty then forget Tomcat. I just happen to use > both... Jetty mostly but sometimes Tomcat when I need to attach library > modules to debug and edit. Live reloading can almost work right in Tomcat > but not like Jetty, instead it does a partial reload (with some complaints > about resources being out of sync), nevertheless it can sort of work. > > >it runs the whole test-compile phase which in my case takes more > >than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > >development. > Are you on windows? what Maven plug-in version are you running? on Ubuntu > it doesn't do this (there are some configuration options on the plug-in, try > uncheck the ones you don't need). > > regards, > Peter > > > ----- Original Message ----- > From: "Hugues Narjoux" <huguesnarj...@gmail.com> > To: "Tapestry users" <users@tapestry.apache.org> > Sent: Wednesday, 18 March, 2009 18:32:20 GMT +02:00 Athens, Beirut, > Bucharest, Istanbul > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > But if you disable the automatic publishing, how would your modifications > be > updated ? I tried it, even with manual publising and I still do not see my > the results of my update ... > I tried the maven jetty plugin like Borut suggested.It works just fine as > for class reloading. Except that every time you restart your server (mvn > jettty:run) it runs the whole test-compile phase which in my case takes > more > than 5 minutes (don't ask why ;) ). Therefore I cannot use it for > development. > > > > > > On Wed, Mar 18, 2009 at 3:39 PM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > > > This is a pain, and has been an issue for years already... and > > unfortunately there is no end in site. There is a minor tweak though, WTP > > has an option (in Tomcat server properties dialog) select 'never publish > > automatically' > > > > regards, > > Peter > > > > ----- Original Message ----- > > From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com> > > To: "Tapestry users" <users@tapestry.apache.org> > > Sent: Wednesday, 18 March, 2009 16:02:50 GMT +02:00 Athens, Beirut, > > Bucharest, Istanbul > > Subject: Re: [T5.0.18] Class re-loading and eclipse debugger > > > > On Wed, Mar 18, 2009 at 10:57 AM, Hugues Narjoux > > <huguesnarj...@gmail.com> wrote: > > > WTP was great here because it > > > would let you configure a deployment descriptor and automaticaly deploy > > and > > > re-assemble your webapp. > > > > I guess the problem is exactly the reassemble process. Many times, > > when using WTP in a Struts (aaaaaaaaaaaaaaaaaargh!) project, it > > wouldn't update the application correctly when I changed one class. > > Then I gave up. I never really deploy an application in development, > > just when really deploying to the production server, not wasting a lot > > of time with it. > > > > -- > > Thiago > > > > --------------------------------------------------------------------- > > 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 > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
