Cascade the paymentResponseItems field
Reorganized imports per Broadleaf conventions
[maven-release-plugin] prepare for next development iteration
#351 - Upgrade FontAwesome to 3.2.1
#352 - Add ability to get foreign key display values from IDs for to-one fields
#352 - Improve general filtering / sorting for admin screens
Resolve anonymous Customers via the database for CustomerState if they have already been persisted
#285 - Ensure that the required field validation works for radio buttons where the field is not actually sent in the POST
#369 - Make the MatchesFieldValidator a Spring bean
#370 - The middle breadcrumb should consider previously applied filters
Move the ApplicationContextHolder into common so that all of the Broadleaf components can utilize it
Add a new EntityListener to Customer that publishes a Spring event when a Customer has been persisted
Refactor a couple of component scans, add a new standard profile-web applicationContext
Refactor the CustomerStateRequestProcessor to use the session-based customer until that Customer has been persisted. Once persisted, the Customer is removed from session and on subsequent updates the CartState is also refreshed.
Merge pull request #365 from BroadleafCommerce/customer-state-fix

Anonymous Customers can be persisted but are not resolved from the database
#363 - Fix broken Redactor select font button
#365 - As a part of the customer state refactoring, do not include the login service as a default scanned bean
(cherry picked from commit 37fd6450f08b6ac88793fffa078e52fc282c128f)
#285 - Ensure that the required field validation works for radio buttons where the field is not actually sent in the POST
#285 - Ensure that the required field validation works for radio buttons where the field is not actually sent in the POST
#377 - For AdminPresentationCollection annotated collections with an addType of PERSIST and an extended polymorphic type, the incorrect type is created upon save