On behalf of the Spring Data team I'd like to announce the availability of the second service release of Spring Data release train Fowler. The release ships 40 tickets fixed and is a recommended upgrade for all users due to an important bugfix in the support for JTA 1.2's @Transactional.

Spring Boot users can upgrade to the new version by setting the spring-data-releasetrain.version property in their Maven POMs to Fowler-SR2, Non-Spring Boot users are recommended to use the Spring Data release train BOM as described in our example repository and configure it to the very same version.

• Spring Data Commons 1.10.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data JPA 1.8.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data MongoDB 1.7.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Neo4j 3.3.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Solr 1.4.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Couchbase 1.3.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Cassandra 1.2.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Elasticsearch 1.2.2 - Artifacts - JavaDocs - Documentation - …

On behalf of the Spring XD team, I am very pleased to announce the general availability of Spring XD 1.2.1!

This release includes bug fixes and some small enhancements:

• Support for registering custom Kryo Serializers
• Configuration options to fine tune Kryo performance
• Update several dependencies to latest versions - Spring Integration, Boot, reactor, Groovy
• Add jars for Avro and Snappy compression to Sqoop job submission
• Fix admin UI access when security is enabled
• Improved pagination for containers and jobs

You can download the zip distribution or install on OSX using homebrew On RHEL/CentOS you can install using rpm…

On behalf of the Spring Security Kerberos team, I'm pleased to announce the release of Spring Security Kerberos 1.0.1. The highlights of the release are:

• Support Spring Security 4
• Support Spring LDAP 2.0
• Fix SPNEGO auth fails if client proposes MS krb5 OID #34

Project Site | Reference | Changelog

I'm pleased to announce the release of Spring Security 4.0.2.RELEASE. This release is the second maintenance release of the 4.0 line and focusses on fixing any major issues that were found in the new release. For complete details on the release, refer to the Change Log.

Along with lots of bug fixes, the highlights of this release include:

Support for Spring Framework 4.2

Spring Framework 4.2 GA is just around the corner. Spring Security 4.0.2 fixes some issues when running with Spring Framework 4.2. We are also rerunning our entire test suite using Spring Framework 4.2.

Minor Improvements to…

I'm pleased to announce the release of Spring Security 3.2.8.RELEASE. This release focusses on fixing major issues. For complete details on the release, refer to the Change Log.

While we will continue to support the 3.2.x line for some time, we encourage everyone to update to 4.x. To make this transition easy, we have a very detailed migration guide complete with sample migrations and a diff. If you have any problems migrating, create a StackOverflow question with the spring-security tag. If you don't get a response within a reasonable amount of time feel free to ping me at @rob_winch or in…

On behalf on the Spring Roo team at DISID Corporation, I am pleased to announce that Spring Roo 2.0.0.M1 has been released!

This first release of Spring Roo 2.0 is a large refactoring of Spring Roo project. We have moved Roo to be a smaller and easier to maintain project:

• The OSGi container has been upgraded to OSGi R5.
• Spring Roo has defined its runtime. The Roo runtime contains everything that is needed to execute addons and it doesn't contain any addon. By not containing any addons it is easier to keep the Roo runtime more stable and backward compatible.
• Today, Spring Roo is centered in Spring technologies - so addons like GWT and JSF have been moved to their own projects in order to be maintained by the Roo community.
• The user guide has been migrated to ASCIIdoc.
…

Dear Spring community,

Spring Framework 4.2 is not going GA today quite yet, but it's almost there: RC3 is available from repo.spring.io now, as a last release candidate before we reach GA on the 30th of July. This release includes 50 fixes and improvements over RC2, waiting for you to try them!

We decided to do another release candidate for several reasons: e.g. our continued wait for Jackson 2.6 final and Hibernate ORM 5.0 final but also our recent build upgrade to Gradle 2.5 and some last-minute refinements within our 4.2 web story (based on RC1/RC2 feedback).

I'm pleased to announce that this is in fact the first release of Spring which builds fine not only on JDK 8 but also on current JDK 9 snapshots! Our master build…

Spring Boot v1.3.0.M2 is available now from the Spring milestone repository. This release closes a whopping 73 issues and merges 59 pull-requests! Thanks to everyone that has contributed.

Highlights of the new release include:

• Auto-configuration support for jOOQ.
• Hypermedia support for actuator endpoints.
• Support for ANSI color banner.txt files.
• An improved way to access ApplicationArguments.
• New /flyway, /liquibase and /logfile actuator endpoints.
• Auto-configuration support for Spring Session with Redis.
• Property based configuration of Spring's "resource chains".
• New logback <springProfile> and <springProperty> tags.
• Support for Apache Artemis (following the donation of HornetQ to Apache).
• A new AntLib module to help create executable jars from Apache Ant.
…

We are pleased to announce that the second milestone for the upcoming 4.2 release of Spring Integration is now available. In addition to those features in milestone 1 this release includes:

##Zookeeper Support

Several components have been added that use zookeeper, including a LockRegistry and MetadataStore but probably the most significant is the ability to assign endpoints to a leadership Role, with the endpoint lifecycle being controlled by the leadership status. When an application context is granted leadership, all endpoints in the corresponding role are started automatically. Similarly…