Hi, Arjan, I've tested the fix with CTS cases. The previously-failed case passed . The reproducer was sent in another mail. Thanks and best regards Ruolin

Hi, A potential fix for the CTS failure has been committed here: https://github.com/javaserverfaces/mojarra/pull/4372 I was waiting for a reproducer for the failure, but as the fix seems simple enough

Hi Arjan, When will you do the merge from 2.3.x to master? at least we need to fix CTS failure issue soon, to be efficient, you can commit the fix firstly in

Hi Bill, I'm sure there are many JSF webapps out there running on Tomcat that simply bundle Mojarra in WEB-INF/lib. Portlet applications in Pluto do not rely on the version of JSF included with the

ren.zhijun@... wrote on 04/27/2018 07:29 PM: Oracle GitHub. Yes. Thanks.

Hi Arjan, Then you will fix the TCK issue in javaserverfaces/mojarra project, I will un-archive the project for your fix commit.( you need to file PR and approve it by yourself)

Unfortunately there's too many people involved in this contribution process and not everyone is aware of everything that's going on. That definitely includes me. What was supposed to

Hi, The API project in master has not been touched, it's 100% identical to the 2.3 branch. But it's always possible an accidental bug has crept in the implementation project that causes faulty

My understanding is that the master isn't passing the JSF 2.3 TCK, perhaps because some API changes have been introduced? Do you expect master to be JSF 2.3 compatible? I think we

Hi, The major difference between MOJARRA_2_3X_ROLLING and master are the number of patches Bauke and Kyle did while the vetting of the master was already in progress. I think MOJARRA_2_3X_ROLLING can

Hi Arjan, In our Github project javaserverfaces/mojarra, MOJARRA_2_3X_ROLLING branch is "119 commits ahead, 297 commits behind master". What's the main differences between the two branches?  The

I would expect that the Java EE server vendors would be providing any required updates to the version of JSF included with their server. That's what Oracle will do for WebLogic. Exactly

Hi Bill, The Liferay Faces team is currently working on JSR 378 which is a Portlet Bridge for Portlet 3.0 + JSF 2.2. The JSR for Portlet 3.0 + JSF 2.3 hasn't yet been filed. Our customers are using

Hi Kyle. We have a plan for how to support older releases but we're still discussing the plan to make sure it's workable. In general, we expect support to move to the Eclipse

Thanks Zhijun, I guess I misunderstood your initial email. Are you saying the the project is only archived temporarily (and oracle has yet to decide how to handle legacy releases)? I thought that the

Hi Kyle, Thanks for your question, during the donation process, if you want to file issue or commit code, you can notify me and I can un-archive the project temporarily for you. The

Hi Ed, We contribute fixes for legacy versions of Mojarra (often for 2.2.x, rarely for 2.1.x, and only for security vulnerabilities in 1.2.x). We want to be able to continue contributing fixes and

Kyle, The intent of changing the status of these repositories is to support the community migration over to Eclipse Foundation, Jakarta EE. It is our goal that all work, evolution and focus supports

Hi, Please be aware that the repository javaserverfaces/mojarra has been archived as this project is now part of the EE4J initiative. All activities are now happening in

Hi Zhijun, Since the public repo has been archived, how does Oracle plan to maintain the 2.3.x, 2.2.x, and 2.1.x versions of Mojarra? How can the community contribute fixes and bug reports for those