I think it is just a matter of notifying the webjars maintainer that there
is a new version. I just did a couple of minutes ago and James responded
immediately. (https://github.com/webjars/webjars/issues/34).

regz,
/dd


2012/11/25 Martin Grigorov <[email protected]>

> On Tue, Nov 6, 2012 at 2:51 PM, Martijn Dashorst <
> [email protected]
> > wrote:
>
> > On Mon, Nov 5, 2012 at 10:42 AM, Martin Grigorov <[email protected]>
> > wrote:
> > > No one objected so I've just updated jQuery to 1.8.2 for Wicket 6.3.0.
> >
> > Would it be prudent to switch to webjars [1,2] instead for including
> > jquery? This would open up managing jquery through maven dependency
> > resolution instead of having to upgrade wicket itself.
> >
> > Martijn
> >
> > [1] http://webjars.org
> > [2]
> > http://search.maven.org/#search%7Cga%7C1%7Cg%3Aorg.webjars%20a%3Ajquery
> >
>
> jQuery 1.8.3 has been released at Nov 13, 2012 and there is no new webjar
> for it.
> For now it seems to be much simpler to handle this dependency management as
> we do it.
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com <http://jweekend.com/>
>



-- 
/* Spelin donut mader if iz ina coment */

Reply via email to