Increment version to 2.3.1.BUILD-SNAPSHOT.
Update README.md
Update primefaces repository
Ensure required test directory is created in GIT and remove javadoc refs to missing home dir
Upgrade JSF Mojarra to version 2.1.7
Update Jsf2FlowFacesContext.isValidationFailed()

Previously isValidationFailed() merely delegated to the wrapped
FacesContext ignoring any errors that may have been added to
Web Flow's MessageContext. After the change isValidationFailed()
checks and returns true if the MessageContext contains errors
or otherwise it delegates.

Issues: SWF-1490
Fix for bean validation messages in BindingResult

Previously Web Flow's BindingResult implementation distinguished
object from field-level errors by checking if the source of the
error is null or otherwise a String. However, class-level bean
validation errors have a field source represented by an empty
String. After this change object and field-level errors are
recognized by checking for String-based field source that is
neither null nor empty.

This commit also contains a fix for spring-faces tests where
in JSF 2.1 the presence of an unreleased FacesContext may
cause some tests to fail.
Fix "embedded" mode to be flow session local.

The "embedded" mode flag, which is used to suppress redirects so
that a flow can be embedded on a surrounding page, was previously
stored as a flow execution attribute. The idea was that a flow can
be launched in embedded mode simply by passing a flow input rather
than having that decision fixed through a static flow definition.

However flow execution attributes are not a suitable place to store
the embedded mode flag since they are globally shared. Instead this
information is now stored a flow session attribute, which means that
each individual session (including subflows) can have be in embedded
mode or not without affecting others
Make AbstractMvcView.shouldValidate() protected

Issues: SWF-1458
Minor fixes

- Add versions to schema references in samples
- Documentation fix
- Remove unused package import
Minor fix in FlowPartialViewContext

The fix ensures that getRenderIds returns a mutable collection as
stated in the contract for the method in PartialViewContext.

Issues: SWF-1480
JSF view root to survive redirect in same state

For JSF 2.0.x Spring Web Flow the view root could not be preserved
across redirects in the same state (e.g. following validation)
because a JSF state saving listener held on to the FacesContext,
which Web Flow releases before the redirect.

This issue was addressed in JSF 2.1
http://java.net/jira/browse/JAVASERVERFACES-1604
which means we can allow the view root to survive the redirect.

Note that the behavior can also be controlled with the
redirect-in-same state flow execution attribute.

Issues: SWF-1502
Add support for PostRestoreStateEvent

A PostRestoreStateEvent should be delivered whenever a JSF view is
restored. Typically we rely on JSF to generate required events but
in this case since WebFlow handles the RESTORE_VIEW phase itself,
we need to deliver this event ourselves.

Issues: SWF-1500
Upgrade sample to PrimeFaces 3.1.1

Issues: SWF-1523
Check request param to recognize JSF 2 Ajax requests

Previously we checked the "Faces-Request" header only.
Now we try to delegate the call to
PartialViewContext.isAjaxRequest() first. If a FacesContext
is unavailble for some reason we also check the
"javax.faces.partial.ajax" request parameter.
Correct spring-binding/.classpath to use IVY_CACHE
Updates to readme, javadoc, and sample poms.

Issues: SWF-1507
Upgrade to Spring 3.1.1
Update repository information in docs
Spring Web Flow 2.3.1 release