:-) Nice analogy. So, how do I use the eclipse debugger with mvn jetty:run?
Is it possible? Can I put a breakpoint in my source and have the application drop into it from mvn jetty:run? If not, I have relegated myself to use the simple tomcat solution for now. The button on an M5 is nice but I'd prefer to *work* on a 1969 muscle car if it means I can actually get under the hood and trace the inner workings (not quite as clever as your analogy, I know ;-) Agree with your sentiment. -Luther On Sat, Sep 27, 2008 at 9:38 AM, Borut Bolčina <[EMAIL PROTECTED]>wrote: > Luther, > > it is true - you can work with WTP and Tomcat 6, but that is like driving > the BMW M5 without the M button being pressed. > > Try running the quick start T5 application with mvn jetty:run and with > WTP/Tomcat. Try changing Start.java and then clicking the refresh button in > the browser. Even in this one page web application with 2 java files it > takes 10-times longer with WTP/Tomcat combo to display the changed Start > page. I can imagine it gets worse with larger apps. > > And here is my point - if one of the main strengths of Tapestry 5 is live > class reloading, then it is of paramount value to tell developers how can > they harness the power in different development environments. This is where > the documentation fails. I also own the Alexander's book and as much as the > book is welcomed, it is outdated and the information given on page 43 is > not > true (at least in present moment): > > "You will see that the change you have made is not reflected by the running > application, because you have changed an HTML file, and not Java code. > Smilar to NetBeans, Eclipse doesn't care about changes in HTML files. One > way to update the application in such case is to follow the advice given > for > NetBeans - make change, even if it is an insignificant one, to some Java > file, and save the file. The application will then be reloaded > automatically." > > This is so not T5-ish. > > If there are many ways to develop T5 web apps, then some of this cases > should be explained clearly as this is IMHO one of the barriers many new > tapestry users are hitting at the very beginning. Of course some cases can > be published on wiki, but the most common two or three must be on main T5 > page - this is where most users start. > > I am filing a JIRA request for documentation improvement: > https://issues.apache.org/jira/browse/TAP5-245 > > Cheers, > Borut > > P.S. The Issues link on T5 page (http://tapestry.apache.org/tapestry5/) is > wrong. It should be https://issues.apache.org/jira/browse/TAP5 > > > 2008/9/26 Luther Baker <[EMAIL PROTECTED]> > > > For what its worth, I've had no trouble running Tomcat 6 with Eclipse WTP > > with MAVEN m2 plugins. > > > > I have NOT had to customize the tomcat instance at all. > > > > -Luther > > > > > > > > 2008/9/26 Jonathan Barker <[EMAIL PROTECTED]> > > > > > > > > I was recently cast out of the Garden of Eden for eating the forbidden > > > fruit: m2eclipse (updated). > > > > > > I was running the old JettyLauncher with the old (and rather limited) > > > m2eclipse, on Eclipse 3.3 / MyEclipse 6.0. Life was good. Easy > > debugging, > > > hot reloading. I had JettyPlus configured so I could take my war file > > > straight from my development system and drop it into a JBoss server for > > > deployment and take advantage of pre-configured DataSources. > > > > > > Alas, the updated and mainly superior m2eclipse removes > > PluginDependencies > > > from your classpath in order to make the execution within Eclipse be > > > virtually identical to what it would be from command-line Maven. > > > > > > That breaks JettyLauncher and Run-Jetty-Run because you need the > plugins > > on > > > the classpath. Other than that, it does avoid some odd situations where > > > things work in Eclipse but not when deployed elsewhere. > > > > > > I think I've figured out my usable alternative with external mvn > > > hightide:run (hightide is a derivative of Jetty, and there is a > hightide > > > maven plugin). It's not as convenient, but it is workable. > > > > > > Jonathan > > > > > > > -----Original Message----- > > > > From: Kevin Menard [mailto:[EMAIL PROTECTED] > > > > Sent: Friday, September 26, 2008 13:59 > > > > To: Tapestry users > > > > Subject: Re: Development Environment > > > > > > > > Hi Borut, > > > > > > > > Please file JIRA issues for these ideas, otherwise they're bound to > be > > > > lost. > > > > > > > > -- > > > > Kevin > > > > > > > > > > > > > > > > On Fri, Sep 26, 2008 at 6:53 AM, Borut Bolčina < > > [EMAIL PROTECTED]> > > > > wrote: > > > > > Hello, > > > > > > > > > > since JettyLauncher is not working with Eclipse Ganymede, this > should > > > be > > > > > mentioned at > > > > > http://tapestry.apache.org/tapestry5/tutorial1/env.html > > > > > > > > > > I looked at http://code.google.com/p/run-jetty-run/ but some posts > > > > suggest > > > > > that it is not working with m2eclipse plugin.But I will try it > out... > > > > > > > > > > It would be a great time saver if tutorial at the above link would > > > > describe > > > > > some different scenarios how developers can set up their > environments > > > to > > > > > benefit from live class reloading. Reading the mailing list there > > seems > > > > to > > > > > be great confussion. > > > > > > > > > > Cheers, > > > > > Borut > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > >
