Hi, Wicket reloads HTML templates only when running in Development mode. Do you run your app in Dev mode ?
On Mon, Mar 25, 2013 at 3:54 PM, Martin Dietze <d...@fh-wedel.de> wrote: > I recently upgraded a legacy project from Wicket 1.4 to 6.6. > > In that project we provide a test system to our HTML designers, > set up as follows: whenever a change is committed into the git, > the test system pulls those changes and copies templates, JS > and CSS files into the webapp. > > It seems like now, after the Wicket upgrade, certain changes in > templates (e.g. changes to the markup of fragments) do no longer > "come through", i.e. it seems necessary to restart the system > before the changes take effect. > > Could it be that this is a problem related to the new way of > dealing with markup in Wicket? Or are we simply running into a > cache problem here? > > If this is indeed related to Wicket's markup handling, is there > any usable workaround? Restarting the system over and over makes > work for our HTMLers rather slow and awkward. > > Cheers, > > M'bert > > -- > ----------- / http://herbert.the-little-red-haired-girl.org / > ------------- > =+= > Man muss das Dreibein hin und wieder loben, dann geht es auch schonmal > runter, > den Muell wegbringen. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
