Thanks for the suggestion but most of the work is done in the process-resources phase. Skipping the tests will not help. But I think this is not related to Tapestry anymore :)
I will try launching jetty using a java class. If I can do this, it will solve all my pbs,,, For reference here is what I intend to do: http://docs.codehaus.org/display/JETTY/Embedding+Jetty http://www.codecommit.com/blog/java/so-long-wtp-embedded-jetty-for-me <http://www.codecommit.com/blog/java/so-long-wtp-embedded-jetty-for-me> Cheers Hugues On Wed, Mar 18, 2009 at 9:44 PM, Robert Zeigler <robe...@scazdl.org> wrote: > 5 minute test compilation?!? Wow... > Ok, so, how about: > > mvn -DskipTests jetty:run > > This will disable the test phase of the app, and, consequently, skip > test-source compilation. > > Cheers, > > Robert > > > On Mar 18, 2009, at 3/1811:32 AM , Hugues Narjoux wrote: > > 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 > >
