Hello Luther, thanks for the informative and speedy reply. I'm going to take things one-step-at-a-time. So far, Igor is right about running the Start.class (as found in the test-classes directory). The only issue now is the Eclipse bug-a-boo about not copying the .HTML files along with the .CLASS files. See RuntimeException included below. As soon as I learn how to turn off the filter I will try your way if this fails. Yes, I am basically looking for anyway of speeding up the: edit, build, deploy cycle. Directly deploying .WAR files is OK once but since I'm trying to develop something for work I'm running out of time quickly. Thanks and regards, David.
----- Original Message ----- From: "Luther Baker" <lutherba...@gmail.com> To: users@wicket.apache.org Sent: Saturday, May 30, 2009 9:36:55 AM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? For what its worth, I run a few Wicket 1.4x projects as within Eclipse/m2plugin and pages, etc refresh just fine. I use the Run/Debug Configurations and create a Maven application and then select the jetty plugin, correct workspace and jetty:run command. There are also Jetty options you can include directly in the POM file that define how and when Jetty should regularly will scan the deployed files ... restarting Jetty if changes detected. What I've described is too different mechanisms for picking up changes ... is that what you're asking for? -Luther On Sat, May 30, 2009 at 7:53 AM, Ben Tilford <bentilf...@gmail.com> wrote: > Something that may be worth trying is mvn jetty:run-exploded > > On Fri, May 29, 2009 at 6:10 PM, Igor Vaynberg <igor.vaynb...@gmail.com > >wrote: > > > like i said, the best way is to right click the Start class and do run > > as java application. you can, of course, do it any other way you like > > - including installing jetty eclipse launcher plugin. > > > > -igor > > > > On Fri, May 29, 2009 at 3:17 PM, David Brown > > <dbr...@sexingtechnologies.com> wrote: > > > Hello Igor, thanks for the reply. Can I just ignore the QuickStart > > embedded jetty and install jetty on Eclipse then do a run-as without any > > issues? Please advise, David. > > > > > > > > > ----- Original Message ----- > > > From: "Igor Vaynberg" <igor.vaynb...@gmail.com> > > > To: users@wicket.apache.org > > > Cc: "david" <da...@davidwbrown.name> > > > Sent: Friday, May 29, 2009 4:51:02 PM GMT -06:00 US/Canada Central > > > Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so > different? > > > > > > why dont you just start the project from eclipse directly using the > > > Start class, that way you get debug and hotswap - which should be the > > > real "student's dream" :) > > > > > > -igor > > > > > > On Fri, May 29, 2009 at 2:53 PM, David Brown > > > <dbr...@sexingtechnologies.com> wrote: > > >> Hello Martin, Jeremy, dev, gurus, users and mortals. I have just > > finished ch. 13 of the WIA.pdf. I have followed closely the reading using > > the wicket-in-action eclipse project. I have the wicket-in-action running > > under the: mvn jetty:run. The wicket-in-action project is redeployed > every > > 60 seconds (a student's dream). After finishing the 13th chapter I > decided > > to leave the nest for the 1.4rc QuickStart. The new QuickStart project > > expanded and imported into the Eclipse workspace no-problemo. The mystery > is > > what am I doing wrong to get the automatic 60 second re-deploy. As it > stands > > now I have to kill jetty, mvn package and then restart jetty (mvn > > jetty:run). I have pasted in the: > > >> > > >> > > >> ************************** > > >> <context-param> > > >> <param-name>configuration</param-name> > > >> <param-value>development</param-value> > > >> </context-param> > > >> ************************** > > >> > > >> from the wicket-in-action web.xml but no change. The Windows cmd > console > > shows the usual Wicket WARNING: running in development mode. I plan to > use > > the wicket-in-action almost verbatim including the Hibernate DAO for my > > current gig. It is probably only a few weeks before they start holding my > > feet to the fire. > > >> > > >> Please advise, David. > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > >> For additional commands, e-mail: users-h...@wicket.apache.org > > >> > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
