The Oracle stuff will likely be in the incubator for a while. I definitely agree that there should be a single subproject that hosts the components. Tobago is a little different but there is some overlap and that needs to be worked on.
I think the big priority now is Maven, a new release and incorporating Tobago into MyFaces. Once we've absorbed Tobago, the next logical step seems to be the ADF donation. There is a lot of work to do there to bring the ADF stuff into alignment with MyFaces but Oracle has said they are willing and able to do the work. My .02 sean On 12/15/05, Werner Punz <[EMAIL PROTECTED]> wrote: > Martin Marinschek wrote: > > That's already a problem with the Tobago component set. > > > > Or, to get more precise, even within the MyFaces component set we have > > overlap - look at t:tree and t:tree2. > > > > We'll still try to workout a solution so that users are not > > overwhelmed with choice - but, right, choice is not categorically a > > bad thing ;). > > > > regards, > > > It indeed is not, the biggest problem is that as it seems there are no > real integration points between the three component sets, > while tomahawk is relatively straight forward in its approach, the other > two to my knowledge use different view handlers which means that they > start to choke if combined with each other (or combined with tiles) > > I think before removing choice making all this stuff work together and > with tiles and facelets might be a bigger priority. > >
