[X] Release 6.9.1 with downgrade to jquery 1.8.3, 6.10.0 with jquery 1.10.1 and migration plugin
We should use the time we have to check if the migration plugin does what is expected before releasing 6.10.0. 6.9.0 is a "bad" release for heavy JavaScript user. __ Cedric Gatay (@Cedric_Gatay <http://twitter.com/Cedric_Gatay>) http://code-troopers.com | http://www.bloggure.info | http://cedric.gatay.fr On Wed, Jul 3, 2013 at 11:27 AM, Martin Grigorov <[email protected]>wrote: > On Wed, Jul 3, 2013 at 12:23 PM, Thomas Matthijs <[email protected]> wrote: > > > > > As we are already considering 6.9.1, I think we should fix this issue > > > > as well in 6.9.1. > > > > > > > > [ ] Release 6.9.1 with downgrade to jquery 1.8.3 > > > > [ ] Release 6.9.1 with jquery 1.10.1 and jquery migration plugin > > > > [ ] Release 6.9.1 with downgrade to jquery 1.8.3, 6.10.0 with jquery > > > > 1.10.1 and migration plugin > > > > [X] Don't fix jquery issues > > > > > > > > > > MyApp#init() { > > > getJavaScriptLibrarySettings().setJQueryReference(new > > > JavaScriptResourceReference(..., > > > anyVersionThatWorksForMeUntilIUpgradeMyAppAndPlugins)) > > > } > > > > > > > > > > How can the user know what version of jquery API wicket is compatible > with? > > > > The best is to run the JS unit > tests<https://github.com/apache/wicket/tree/master/wicket-core/src/test/js > > > with > the version of jQuery you'd like to use. > I have ran them with 1.7.2, 1.8.2/3, 1.9.1, 1.10.0, 2.0.1 >
