Re: MyFaces: Retire 3.0 (possibly 2.3?)

If we support 2.3, we can easily support 3.0 - its the same codebase. TomEE e.g. with 2.3 is EOL, whereas 9.0 with MF 3.0 is the current stable version. This will propably change after the first 10.0 version. Same as 2.3-next and 4.0, 4.1 and 5.0 is the same codebase. Melloware Inc schrieb am D

Re: MyFaces: Retire 3.0 (possibly 2.3?)

I am +1 for supporting 2.3. But -1 for 3.0. I guess 17% running 9.0 shocks me as it was just a namespace change?   In fact my clients didn’t even bother with it and just waited for 4.0 final.  Arjun and Balus said it was more for libraries and containers to practice the new namespace it was not mea

Re: MyFaces: Retire 3.0 (possibly 2.3?)

Hi, I would like to see MyFaces continue to actively support both MyFaces 2.3 and MyFaces 3.0 until there is a time when we see the use of these releases drastically decrease. Looking at the 2023 Jakarta EE Survey

Fwd: MyFaces: Retire 3.0 (possibly 2.3?)

Team, As the Mojarra team has completely stopped supporting the 2.3 and 3.0 branches should MyFaces as well? Arjan and Balus said that 3.0 was just the namespace change and no one should be using it in production; they should be on 4.0 at this point now that it is official. As for 2.3 retiring I