See the release notes for what was fixed. If you want to download it, see this page for more information.
Since JSF 2.2 we consider the old style @ManagedBean annotation deprecated, but what now you would say? Well it is pretty straightforward.
1. Change @ManagedBean(name="xxx") to @Named("xxx")
2. Change the package imports for your @XXXScoped annotations to the CDI equivalents.
Since Mojarra is available as a standalone JAR you can opt to update your Glassfish installation with a newer version. How would you do that? Well it is simple.
Make sure your Glassfish container is not running
Grab the latest JAR from http://repo1.maven.org/maven2/org/glassfish/javax.faces/
Replace the javax.faces.jar in the modules directory of your Glassfish directory with the downloaded JAR...
Sometimes when you are working with JSF you might need to understand what is happening beneath the covers. It could be because you think a component is misbehaving and you want to make sure that is the case before you file a bug. To facilitate this you can turn the logging up and in Mojarra there are several loggers that you can use.
The following is a non-exhaustive list:
If you are having a problem with your JPA queries and you are trying to understand what SQL queries it actually sends below the covers you can configure the JPA runtime to show the actual SQL statements it sends over. How? Well for EclipseLink you would add the following to your persistence.xml file.
<property name="eclipselink.logging.level" value="FINEST"/>...
For you folks following this blog be aware Mojarra 2.2.4 was released a little while ago!