I'm trying to provide transparency into Mojarra development practices and increase Mojarra code quality. To that end, this blog entry summarizes the current state of the Hudson jobs for Mojarra.
In an effort to promote my continuing belief that standards are for standardizing, and not innovating, I am announcing the start of the JSF 2.2 JSR effort with a blog entry mostly copied from the entry announcing the start of the previous iteration of the JSF JSR
In my last post, I announced that we had made a release candidate available for Mojarra 2.1.0.
While we work on the release notes and get ready to prepare a release bundle, I wanted to push this quick blog entry out as soon as I could. I just committed the integration of Mojarra 2.1.0 build 10 to the GlassFish 3.1 HEAD, it will be in the next promoted build of GlassFish.
Last week, I sent a code review request to the Mojarra dev list.
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.
In order to bring the testing matrix for Mojarra more in line with Oracle’s current engineering investment, we are planning to have all future Mojarra builds that are targeting the upcoming JSF 2.1 specification only support JavaSE 6 and beyond. Any 2.0.X and 1.2 builds will still continue to be built with Java SE 5.
I'm organizing my thoughts for my JavaOne talk HyperproductiveJSF 2.0 and I want to build the talk around the most common waysthat time is wasted when using JSF in a project. I've talked to lots ofusers, in many different kinds of organizations over the years but it'shard to organize the stories.
With very little pomp and only extenuating circumstance, we are releasing Mojarra 1.2_15.
JSF 2.1 Build 01 integrateg into GlassFish nightly
This quick entry announces that we've started work on JSF 2.1 in earnest.