On Wed, Jun 15, 2011 at 11:25 AM, Martijn Dashorst <[email protected]> wrote: > On Wed, Jun 15, 2011 at 9:14 AM, Martin Grigorov <[email protected]> wrote: >> What do you think about moving wicket-velocity project to WicketStuff >> (Github) ? >> It seems to be not very used by our users, otherwise I'd expect more >> bug reports about it. >> >> Pros: >> - shorter build time > > By how much? 9secs here > >> Cons: >> - none?! > > - no links to existing Apache communities > - moving this functionality to external, how do we validate the core > functionality still works as expected? with unit tests as it should be > - few bug reports mean also a stable integration. There's no baggage > to take care of IMO true, but even then I'd expect feature requests > > I'd rather (re)move things that take a lot of effort on our side, but > which have good alternatives, e.g. ModalWindow, Tree, etc. to github. I'm +100 for this (including Autocomplete in the pack) but the recent contest at wicketinaction.com have several "I'd like more components out of the box" in the comments. In the same time there is a parallel thread suggesting Autocomplete-Object to get into core ... > > Martijn >
I'm not strong about moving velocity integration to WicketStuff. As you said it doesn't take much of my time. I just have the feeling that it is not very used. -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
