> I think it is OK to upgrade to 1.8.2 for Wicket 6.3.0 +1 Thanks, Sebastien.
On Fri, Nov 2, 2012 at 9:18 AM, Martin Grigorov <[email protected]>wrote: > Hi Brian, > > The new Wicket Ajax .js files were implemented and tested with jQuery > 1.7.x and that's why we released them with 1.7.2. > The only policy that I followed is to use jQuery version X.Y.Z where Z > is as big as possible, i.e. more stable. For example if jQuery 1.9.0 > is released I'd suggest to wait for 1.9.2 or 1.9.3 before upgrading. > I have ran the JavaScript tests with jQuery 1.8.0 a month or two ago > and all of them passed. So as far as Wicket is concerned I think it is > OK to upgrade to 1.8.2 for Wicket 6.3.0. If some application uses > plugins which cannot work with 1.8.2 then they can provide custom > ResourceReference with jQuery 1.7.2 and continue using it. > This is valid for WiQuery and other similar libraries too. > > On Thu, Nov 1, 2012 at 11:10 PM, Brian Laframboise > <[email protected]> wrote: > > Now that Wicket is built on top of jQuery, does the Wicket project have a > > stated policy on when that dependency will be updated? > > > > I found the Wicket Ajax page ( > > https://cwiki.apache.org/WICKET/wicket-ajax.html) but it did not address > > this. > > > > I'm aware that I can override the default version included by Wicket. > > However, I would prefer to use the jQuery version that is a) officially > > supported by the team as well and b) ostensibly tested against by > > supporting Wicket projects such as Wicket Stuff and WiQuery. > > > > I can already infer that it's not "guaranteed to be the latest" as the > > Wicket 6.x line is on 1.7.2 while 1.8.0 was released just under a month > > before Wicket 6.0.0 was released ( > > http://en.wikipedia.org/wiki/JQuery#Release_history), and the current > > Wicket 6.2.0 is still on jQuery 1.7.2. > > > > Please note that I'm not complaining; in fact, the stability of the > jQuery > > dependency can be considered a positive. > > > > In my particular case, once upgraded to Wicket 6, our project will > > inevitably have non-Wicket-related jQuery code that depends on the > version > > of jQuery provided by Wicket. Knowing how stable that dependency will be > > will help up plan the testing effort around future Wicket upgrades. > > > > My guess is that the Wicket 6.x line will use jQuery 1.7.2, and only when > > Wicket 7 is released will jQuery be upgraded to >= 1.8.0. > > > > Can anybody confirm this? > > > > Thanks, > > Brian > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
