IMHO if we make it a module them you will have new versions even no changes are produced and for users it will be clear what version to use: the latest one for corresponding wiquery branch.
On Mon, Nov 2, 2015 at 1:42 PM, Guillaume Smet <[email protected]> wrote: > IMHO a separate module similar to what you did with wiQuery would be fine. > Releases are not synchronized with wiQuery releases. > > On Mon, Nov 2, 2015 at 1:13 PM, Martijn Dashorst < > [email protected] > > wrote: > > > Do you want this as a module inside wiquery? > > > > Martijn > > > > > > On Mon, Nov 2, 2015 at 12:26 PM, Guillaume Smet > > <[email protected]> wrote: > > > Hi, > > > > > > I saw that wiQuery has been migrated to Wicketstuff by Martin and > Martijn > > > (thanks!), I was wondering if we could move wiquery-jqplot too? > > > > > > The official repo is here: > > > https://github.com/hielkehoeve/wiquery-jqplot > > > > > > My company maintains a fork here which is compatible with Wicket 7: > > > https://github.com/openwide-java/wiquery-jqplot/commits/owsi > > > > > > Once the official repo is migrated to wicketstuff, I can work on > cleaning > > > up our commits and propose PRs with the fixes/improvements we made in > the > > > last 2 years. > > > > > > I cced Hielke to have his opinion about this. > > > > > > -- > > > Guillaume > > > > > > > > -- > > Become a Wicket expert, learn from the best: http://wicketinaction.com > > > -- Regards - Ernesto Reinaldo Barreiro
