Can someone please backport the involved patch to the release branch? I barely have time to build the release, so any help in the fixing area will help us all.
That is why I don't want to redo from scratch -> it would effectively kill all effort in building the release, and will cost me a full evening to do again. The earliest that I can rebuild is on friday. Martijn On 8/22/07, Al Maw <[EMAIL PROTECTED]> wrote: > Jean-Baptiste Quenot wrote: > > * Al Maw: > > > >> [x] no, the modification watcher for properties was broken, and > >> that's a sufficiently major issue that we can't possibly release > >> beta3 with that in it. > >> > >> Sorry. :-( > >> > >> The issue seems to have been added by someone in r565035 on > >> August 12, and I've just fixed it in r568603. I'm not sure how > >> no one else has managed to spot this in the meantime... > > > > ModificationWatcher also happened to be broken a few months ago > > (it was another problem though). The fact is that by default it's > > not activated. You have to specify the source folder for this to > > be activated. This may explain why nobody noticed. > > > > Or do you use a stock Wicket? > > It's activated with a perfectly stock Wicket provided you run in > development mode - that's what allows you to update properties and > markup on the fly while you're developing. > > Maybe not many people use the properties-based i18n support. > > Regards, > > Al > -- > Alastair Maw > Wicket-biased blog at http://herebebeasties.com > -- Wicket joins the Apache Software Foundation as Apache Wicket Apache Wicket 1.3.0-beta2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/
