Create a new application using the Quickstart guide: http://wicket.apache.org/start/quickstart.html
Run the Start.java application right from Eclipse in debug mode. Hot code replacement from src/main/webapp/* should work now. Best regards / Met vriendelijke groet, Kees van Dieren Squins IT Solutions BV Oranjestraat 30 2983 HS Ridderkerk The Netherlands Mobile: +31 (0)6 30413841 www.squins.com Chamber of commerce Rotterdam: 24435103 2014-02-15 16:12 GMT+01:00 Igor Vaynberg <igor.vaynb...@gmail.com>: > Make sure wicket is running in development mode. It will scan resources for > changes. A refresh in the browser will load the latest version. > > -igor > On Feb 14, 2014 3:59 PM, "tertioptus" <benpaige...@hotmail.com> wrote: > > > I use Jetty, maven and Eclipse. > > > > *What's the best way for me to have Jetty pick up my changes from a > > JavaScript file not in the war project?* > > > > Currently, I have clean install both projects and then restart jetty to > see > > changes. > > > > I am assuming this is common among Wicket users with the advent of > > component > > bound resources. > > > > -- > > View this message in context: > > > http://apache-wicket.1842946.n4.nabble.com/Jetty-Wicket-and-getting-live-JavaScript-changes-tp4664472.html > > Sent from the Users forum mailing list archive at Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > >
