Dear Spring Community,

We are pleased to announce the release of Spring Social 1.0.0.RC2. Spring Social lets you connect your Java applications to Software-as-a-Service (SaaS) providers such as Facebook and Twitter.

This announcement is for the Spring Social core project as well as the Spring Social Facebook and Spring Social Twitter projects which are also seeing their 1.0.0.RC2 releases today.

This release includes fixes for bugs reported since 1.0.0.RC1, as well as a few improvements:

• The Twitter and Facebook clients now support paging for API operations that can return paged results.
• ProviderSignInController now handles the scenario where the user denies authorization.
• The exceptional case where multiple local users are matched during a provider sign in attempt is now handled.
• The set of sample applications has been updated.

See the change logs for more information on what's new in this release (Core | Facebook | Twitter)

To get the software, download the release distribution (Core | Facebook | Twitter) or simply add the maven artifacts to your project. To see it live, run through the quickstart and spin up the showcase app (updated for 1.0.0.RC2). Supplement as you go with information from the reference manual.

Spring Social requires Spring Framework 3.0.5 or > to run. We recommend Spring 3.1 for new applications to take advantage of the latest advances in the core framework. See the reference manual for a full description of dependencies.

Many thanks to the community for helping us shake out and resolve issues in RC1. As we move toward the GA release, we appreciate the community involvement and are eager to hear your thoughts on this RC2 release. Participate in the forum or, if you have any suggestions or find any bugs, post them in the issue tracker.

We hope you enjoy using Spring Social!