We are pleased to announce the release of the first milestone of Reactor Kafka 1.0.0.

What is Reactor Kafka?

Reactor Kafka is a reactive API for Apache Kafka based on Project Reactor. Reactor Kafka API enables messages to be published to Kafka topics and consumed from Kafka topics using functional APIs with non-blocking back-pressure and very low overheads. This enables applications using Reactor to use Kafka as a message bus or streaming platform and integrate with other systems to provide an end-to-end reactive pipeline.

The value proposition for Reactor Kafka is the efficient utilization of…

We’re pleased to announce a release of Spring Statemachine 1.2.0.RELEASE. Artifacts are available either from Maven Central or from Spring Repository.

Let's see what we did for this initial 1.2.x release

• Usual bug fixes and small enhancements.
• Support for UML submachines.
• New Spring Data Repository abstraction keeping machine configurations in an external repository with built-in support for Redis, MongoDB and JPA.
• New samples.
• New support for state do actions.
• New monitoring and tracing API's.
• Initial support for Spring Boot auto-config.
• New transition and state error action concepts.

There's no changes from a final release candicate but full history is available from changelog…

We are pleased to announce that the first milestone for the 5.0 version of Spring Integration is now available.

This is a new major version, based on Spring Framework 5.0 and requires Java 8; this is the biggest change so far, but the following are also included:

• The Java DSL is now rolled into the framework itself; there are some minor changes to the DSL, such as the removal of the .handleWithAdapter() methods and some general Factory classes. A complete discussion of the DSL changes can be found in the Migration Guide.

• Upgrade to Spring Data Kay.

• Upgrade to Spring AMQP 2.0.

• First class support for TCP/UDP has been added to the DSL.

• Spring Integration is now based on Reactor 3.0 and Messaging Gateway Promise methods now have to be changed to return Mono.

• You can now configure mid-flow transactions via TransactionHandleMessageAdvice for adviceChain Messaging Annotations attribute and <transactional> sub-element when using XML configuration.

  …

We’re pleased to announce a release candicate of Spring Statemachine 1.2.0.RC1. Artifacts are available from Spring Repository.

What we got into this release:

• Usual bug fixes and small enhancements
• New api's for tracing and monitoring
• New monitoring sample
• Full repository config support for Redis, MongoDB and JPA
• Boot auto-config enhacements
• Lot of documentation enhacements

Full changes as usual are available from changelog. We're planning to fire up 1.2.0.RELEASE before xmas and possibly do a second release candicate if any major issues are found.

Thank you for all who have contributed in…

We are pleased to announce the first milestone of Spring AMQP 2.0 is now available.

For a complete list of changes; see the what’s new in the reference manual and the release notes.

Here are some highlights of this release

• The framework is now fully Java 8 based; several functional interfaces are provided for convenient Lambda implementations (callbacks, ReplyingMessageListener etc). Java 8 is now a requirement. It is also based on Spring Framework 5.0.

• The framework uses the new 4.0 amqp-client library.

• A new DirectMessageListenerContainer is now available alongside the existing SimpleMessageListenerContainer. The new container actually has a simpler architecture and the listener is called directly on the amqp-client thread (hence the name Direct…​). See Choosing a Container to help you decide which container is appropriate for your application.

  …

On behalf of the team, I am pleased to announce that Brixton Service Release 7 and Camden Service Release 3 of Spring Cloud are available today. The releases can be found in our Spring Release repository and Maven Central.

These releases include primarily bug fixes.

The following modules were updated as part of Brixton.SR7:

• Spring Cloud Config 1.1.3.RELEASE
• Spring Cloud Netflix 1.1.7.RELEASE
• Spring Cloud Sleuth 1.0.11.RELEASE

The following modules were updated as part of Camden.SR3:

• Spring Cloud Commons 1.1.6.RELEASE
• Spring Cloud Config 1.2.2.RELEASE
• Spring Cloud Netflix 1.2.3.RELEASE
• Spring Cloud Consul 1.1.2.RELEASE
• Spring Cloud Sleuth 1.1.0.RELEASE
• Spring Cloud Contract 1.0.2.RELEASE
…

On behalf of the community, I’m pleased to announce the release of Spring Session 1.3.0.RC1. This release release closes lots of community submitted Pull Requests. For a complete list of changes see the changelog.

What’s New in Spring Session 1.3.0 RC1

Highlights include:

• First class Spring Security’s RememberMe Support

• Updated guides to use Lettuce

• OrientDB Support

• Configuration Improvements

• Performance Optimizations

• Bug Fixes

Contributions

Without the community we couldn’t be the successful project we are today. I’d like to thank everyone that created issues & provided feedback…

On behalf of the Spring Cloud Data Flow team, I am pleased to announce the 1.1.0.RC1 release of Spring Cloud Data Flow for Apache YARN.

Spring Cloud Data Flow for Apache YARN allows one to use all the goodness of Spring Cloud Data Flow (like the Shell and UI) while targeting Apache YARN as a backend. Stream components are deployed as individual apps in Apache YARN, leveraging the power of the platform to handle scaling and health monitoring.

This first release candicate

• Builds upon Spring Cloud Data Flow 1.1.0.RC1 and Spring Cloud Deployer 1.1.0.RC1.
• Support for keeping multiple deployer versions in hdfs.
• Preparation of supporting upgrades on Ambari when these become available with Ambari future versions.
…

On behalf of the Spring Data team, I’d like to announce the first milestone of the Kay release train. This is a special release train as it's going to ship a new generation of Spring Data that will include a couple of breaking changes going forward.

Infrastructure upgrades

The first and most noticeable change is the upgrade to Java 8 as a minimum baseline (no JDK 6 compatibility anymore) and an upgrade to Spring 5 as framework foundation. In subsequent milestones we're going to ship some significant internal rewrites that will also affect user facing API to make use of the new language…