a) remove the old (kinda unsupported) tree from extensions (is anyone even use it?)
+1
b) move the current Tree and TreeTable* from core to extensions (sight, i know we moved it into core just recently)
Don't know yet.
c) move the new Tree into core.
So the 'new new' tree is incompatible with the 'new' tree? Why can't you just give them different names and let them live together in a package? One of the anoying things currently is that you have to ask people whether they are working with the core or extensions tree; I bet that's as confusing for users as it is for us. Imho, it would be better to just delete the old one and keep all the trees we're gonna support in core projects together in one package so that users can find them more easily and compare their features.
* I don't think it's a good idea to have a TreeTable in core anyway. We don't have DataTable in core and I'm pretty sure much more people are using DataTable then TreeTable.
If I remember correctly I argued for moving everything related to repeaters to core a while ago. The initial idea was always that extensions was either for components that you rarely use in a project, or for components that need to 'mature' a bit. I don't think the latter is a very good idea anymore (we could have wicket-stuff projects instead) and imho, any component that you'd almost always use in any project could go to the core project. Datatables definitively fall into that category. And trees... well it is still my opinion that they have a place in lots of projects. Core is fine with me. Eelco
