...
Even if there is interest, a TLP would not prevent a merge of the two, unless
Trinidad doesn't want
to or the MyFaces PMC doesn't want to. If all Tomahawk developers would like to
merge with Trinidad
and Trinidad wants to and the MyFaces PMC doesn't, there are other issues :)
We started
...
FWIW, I think Trinidad is more compatible with Tomahawk
then Tobago is... they don't work perfectly together, but I'd
very much like to see the incompatibilities resolved.
there was also an idea of a myfaces commons lib, which contains
non-renderkit features like validators and
On the other hand, if Trinidad wants to be a (Dare I say The?)
general purpose component set, then MyFaces community acceptance is
probably a good target to hit. That's going to happen better as part
of the MyFaces community rather than as an independent TLP. The
ad-hoc approach taken thus far
Adam,
Actually the reason for the switch to List versus Iterable would be for
general convenience of developers consuming the api (with efficiency a
much smaller issue).
Which methods on java.util.List do you think are providing too broad of
a contract? Do you believe that returning a List
I don't think there's that much reason not to return
a List. All I'm saying is that if you had an API
that was Iterator, and your desire was to support
the fun SE 5 for construct, then Iterable is the
simplest change. The question then is why the
original API was ever Iterator, and if it should
