I haven't developed in Eclipse for a little while now, but IIRC, you can add T4 as another project to your workspace. Then make your project depend on Tapestry (the m2eclipse plugin may do this automatically). At that point, you can just use the JettyLauncher plugin to run and debug your application, stepping into Tapestry code if you need to.
-- Kevin Menard Servprise International, Inc. Remote reboot & power control for your network www.servprise.com +1 508.892.3823 x308 > -----Original Message----- > From: Ulrich Stärk [mailto:[EMAIL PROTECTED] > Sent: Monday, February 18, 2008 10:10 AM > To: [email protected] > Subject: howto debug with tapestry4 trunk from svn > > I'd like to debug T4 inside Eclipse using a small Maven managed web app > and the Maven Jetty plugin. > I'm perfectly able to do so like this: > > 1. update local T4 copy > 2. install T4 into local Maven repository. > 3. start the Maven Jetty plugin with the VM being in debug mode and > have > Eclipse connect to that VM. > 4. debug the problem and make changes to Tapestry code > 5. goto 2. > > So every time I make changes to Tapestry's code I have to re-install it > into my local repository. > > Is there any way to avoid this? Like some mechanism to tell Maven to > not > try to load the dependency from the repository but rather directly from > some class path? Or should I use a completely different approach > instead > of using Maven's Jetty plugin? > > Any suggestions are highly appreciated. > > Uli > > > --------------------------------------------------------------------- > 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]
