remove from core: -1 > - FormComponentFeedbackBorder -1 > - AbstractUploadForm, FileUploadForm -1 > - PagedTableNavigator, SortableTableHeader, SortableTableHeaderGroup, -1 > SortableTableHeaders, TableNavigationIncrementLink, -1 > TableNavigationWithMargin, +1 > WicketComponentTree 0 > - SignInPanel
I think there will always be a discussion on what is really core functionality and what is not (contrib). The main reason for that voting: I don't know yet how wicket-contrib will be organized and managed (no time to check the new project). Are we simply separating the current sources into two projects? Will the package names remain the same? Is it because there will potentially be different developers / maintainers responsible for it? Where exactly do we draw the line between core and contrib? May be contrib is not the right name than. May be wicket-components or wicket-base. Contrib to me implies something like a database of contributions provided by anybody with the contributor responsible to maintain it, not the Wicket team. Juergen ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Wicket-develop mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-develop
