



The first release for Jakarta EE (under the EE4J project) of Mojarra is imminent. This release will be called 2.3.9, and a pre-release jar can be found here:









A tiny bit of background on how this version came to be:





Originally we had the https://github.com/javaserverfaces/mojarra/tree/MOJARRA_2_3X_ROLLING branch from which Mojarra 2.3 versions were being released.





At some point we started the cleaning and vetting process for the transfer from Oracle to Eclipse. This was done from the master branch, which at the time was up to date with Mojarra 2.3.3. I temporarily named this version 2.4-SNAPSHOT to distinguish it, and not yet being sure what the new version was going to be. The JSF version (API) of course stayed at 2.3.





In hindsight calling it 2.4 wasn't the best choice as it caused quite an amount of confusion, so I'd like to apologise for that.





The cleanings conducted in master were largely about license adjustments, removing tons of unnecessary artefacts (a lot of unused jars that the ancient ant scripts used, examples, pieces of an old web site, some experimental demo code, etc, etc). The ant scripts were also removed, although essentially the core parts of them were inserted in the main Maven poms and still executed via ant-runner. An amount of refactoring of the implementation code was done as well (mostly addressing sonar warnings and formatting).





Meanwhile, the MOJARRA_2_3X_ROLLING branch was still open, and various commits were done to that branch as well as releases 2.3.4, 2.3.5, 2.3.6 and 2.3.7 were done from it).





When the transfer work in the javaserverfaces master was almost done, a version representing that last state was released. However, unfortunately this release appeared as 2.4.0 on Maven central, and even more unfortunately the master pom was neither removed from the Mojarra pom, nor was it deployed. As it appeared, it's virtually impossible to deploy anything to the com.sun namespace on Maven central, so the 2.4.0 releases is essentially botched (we perhaps should try to get it removed).





After Mojarra landed on Eclipse ( https://github.com/eclipse-ee4j/mojarra ), there was a special EE4J_8 branch created, which according to the transfer conditions was the branch dedicated to the initial release of GlassFish 5.1. This is the version that's essentially a re-release of GlassFish 5, but "just" re-licensed to Eclipse. From the EE4J_8 branch we started off with the temporary version 2.3.99, which incremented to 2.3.3.102.





For the first Jakarta EE/EE4J release the version in the EE4J_8 branch was eventually re-aligned with the last version from the MOJARRA_2_3X_ROLLING branch, and the intermediate changes had been ported over.





So, after this long story, we'd arrived at Mojarra 2.3.9. Mojarra 2.3.9 has the same Java packages as the Oracle version, but it has different Maven coordinates as required by the Eclipse PMC:





The full jar will be at:

<groupId>org.glassfish</groupId>

<artifactId>jakarta.faces</artifactId> <version>2.3.9</version>

API only will be at:

<groupId>jakarta.faces</groupId> <artifactId>jakarta.faces-api</artifactId> <version>2.3.1</version>

Parent pom will be at:

<groupId>org.glassfish</groupId> <artifactId>mojarra-parent</artifactId> <version>2.3.9</version>





If I'm not mistaken there will be at least one more update in the EE4J_8 branch, and that's to update all the javax.* dependencies to their corresponding jakarta.* coordinates.





It would be great if the Mojarra committers and everyone else interested in JSF and Mojarra could test the 2.3.9 pre-release a little. Thanks in advance!





Kind regards,

Arjan Tijms

















































Hi,