Are we sure it is 2.9 and not 2.4? We might want to check that just to be sure I'm not saying it is incorrect I just didn't see it going to 2.9.
Thanks, Paul Nicolucci On Fri, Nov 15, 2019 at 11:35 AM Thomas Andraschko < [email protected]> wrote: > AFAIK Jakarta 9 will contain JSF 2.3 with Jakarta namespace + version > bumped to 2.9. > I dont think that this is huge effort. Just fork 2.3 and rename everything. > > Current 3.0 Targets Jakarta10 / JSF 3 with removed Faces EL, Managed Beans > and heavy cleanup. > > I would do this: > - release 3.0 M1 with javax, the current code ist stable, faster, smaller > and OK to use > - fork 2.3 as 2.9 and change to Jakarta package and do 2.9M1 > - Change Jakarta namespace on 3.0 and do a 3.0M2 > > > Paul Nicolucci <[email protected]> schrieb am Fr., 15. Nov. 2019, > 17:18: > >> Hi, >> >> I think we also need to start thinking about the package name changes >> from javax.faces to jakarta.faces for the API. This would be a change that >> would certainly be in JSF 3.0 whenever that specification comes out >> (Jakarta EE 10?). In addition I think the Jakarta community is looking to >> release Jakarta EE 9 which would just be Java EE 8 with the API package >> name change javax->jakarta so we need to start looking at a Jakarta 9 >> branch perhaps in the MyFaces code base. I would think that the Jakarta EE >> 9 changes would more than likely jump the JSF spec version to 2.4. >> >> In my opinion we should hold off on a release, review the Jakarta >> information and make any necessary changes to the MyFaces code base as the >> Jakarta projects move forward. >> >> For the current Jakarta EE 9 Status see: >> https://github.com/eclipse-ee4j/jakartaee-platform/blob/gh-pages/minutes/2019-11-12.md >> >> Thoughts? >> >> Thanks, >> >> Paul Nicolucci >> >> On Mon, Nov 4, 2019 at 2:36 PM Thomas Andraschko < >> [email protected]> wrote: >> >>> JFYI: >>> i think i'm finally "done" with the refactorings. >>> I will start with a release vote the next days. >>> >>> >>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >>> Virenfrei. >>> www.avast.com >>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >>> <#m_853411485417842697_m_8209636381781010786_m_-2701175102028896175_m_1314111415991572004_m_119743608639799328_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >>> Am Sa., 20. Apr. 2019 um 09:27 Uhr schrieb Werner Punz < >>> [email protected]>: >>> >>>> +1 from my side. I will add a bunch of additional client tests after >>>> easter. >>>> >>>> Am Fr., 19. Apr. 2019 um 21:44 Uhr schrieb Thomas Andraschko < >>>> [email protected]>: >>>> >>>>> Hi, >>>>> >>>>> WDYT about release a M1? >>>>> >>>>> The current master received a BIG cleanup compared to 2.3 and we >>>>> already removed @ManagedBeans and Faces EL. >>>>> I also introduced integrationtests and Werner provided many tests for >>>>> the client side. >>>>> >>>>> I think its a good time to release a M1 and maybe get some feedback. >>>>> Maybe also a good promotion that we currently more active as competitors >>>>> ;) >>>>> >>>>> Best regards, >>>>> Thomas >>>>> >>>>> >>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >>>>> Virenfrei. >>>>> www.avast.com >>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >>>>> <#m_853411485417842697_m_8209636381781010786_m_-2701175102028896175_m_1314111415991572004_m_119743608639799328_m_129114922430811379_m_-3822526704907192759_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>>>> >>>>
