Hi There is an alternative to do it for 2.0.x / 2.1.x . We can create a temporal 2.2.x branch that will only contain JSF 2.1 + JSF 2.2 windowId API and then we do milestones releases, which does not require to be official (no TCK), with some additional identifier. For example myfaces-bundle-2.2.0-mr-1w.jar or something like that.
In this way, we can just implement the proposal we have for JSF 2.2, and people could try it, but we avoid the overhead involved in implement myfaces specific hacks for 2.1. Later, we can backport it to JSF 2.1(optional), but only after we have a clear idea about how the implementation should work, and how we can backport it. Does that sounds reasonable? regards, Leonardo Uribe 2012/7/23 Gerhard Petracek <[email protected]>: > hi @ all, > > if there are no objections, i'll create a jira ticket for it tomorrow. > > regards, > gerhard > > http://www.irian.at > > Your JSF/JavaEE powerhouse - > JavaEE Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > > > > 2012/7/20 David Blevins <[email protected]> >> >> >> On Jul 19, 2012, at 2:49 AM, Mark Struberg wrote: >> > The internal API will be 1:1 sync with the proposed javax.faces API - we >> > are just not allowed to do it directly in javax.faces before it's official. >> >> Sounds great. Only reason I ask was the TCK gets cranky when you change >> the API signatures. But this proposed approach sounds like a nice >> compromise. >> >> Very workable. >> >> >> -David >> >
