As you may have noticed, Oracle’s java.net collaboration site is undergoing an infrastructure provider change. More details on this can be found on Sonya Barry’s blog. For Mojarra JSF, this transition is only partially complete. I plan to publish a new entry (and update the Spec and Mojarra JSF FAQ files) when it’s all done describing everything you need to know to participate in the Mojarra JSF community, but you can consider this blog entry a preview.
First off, I am very happy to announce the existence of an externally visible Hudson job for Mojarra JSF 2.1.0 running on the very latest GlassFish 3.1 build. This job is visible at <http://hudson.glassfish.org/job/JSF2.1-GF3.1/>. I’m very proud to report that the Mojarra community’s continuing dedication to test driven development has resulted in us having 1,876 tests at last count. These tests use Cactus, JUnit, and HtmlUnit. The presence of this Hudson job will add another step to the responsibilities for comitters, which I learned from my days using Tinderbox as a developer on Netscape 6: don’t check in unless the Continuous Integration job is clean.
The new java.net features Mike Cannon-Brookes’s excellent JIRA issuetracking software. In addition to being a dashingly handsome software professional, Mr. Cannon-Brookes has crafted the world’s premiere issue tracking software. JIRA is a vast improvement over issuezilla. As before, we have separate issue trackers for the JavaServer Faces Specification and Oracle’s Mojarra JSF implementation.
Unfortunately, we cannot yet join the cool kids using git so we still use subversion.
The SVN url for the Mojarra HEAD, which implements the very latest version of the specification, is <https://svn.java.net/svn/mojarra~svn/trunk>. Maybe we’ll get to git some day.
The Mojarra community is still alive and well. There have been infrastructure changes, and there will be more (mailing lists, for example). The FAQs will be updated when these changes are complete.