I've managed to avoid dealing with multiple versions of jQuery on the same page. That sounds like a Bad Idea, and probably not necessary since in my experience jQuery does a good job being backwards compatible. But if you really must, http://api.jquery.com/jQuery.noConflict/ may be your ticket.
On Sun, Mar 24, 2013 at 11:22 PM, Harrie Hazewinkel <[email protected]>wrote: > Hi Dan, > > Thanks for the example. > > On Mar 24, 2013, at 7:26 PM, Dan Retzlaff <[email protected]> wrote: > > Re: duplicate/conflicting contributions, Wicket automatically de-dups > > header contributions. See HeaderItem#getRenderTokens(). Since Wicket > itself > > pulls in JQuery, your app's use of it should be configured > > through IJavaScriptLibrarySettings as shown here. > > Is that still the case when you have components that use different > versions of > jQuery, because the components come from different libraries? > Guess not, but will give it a try. > > > > > Harrie > [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
