It's my pleasure to announce that the first milestone of Spring REST Docs 1.1 has been released. 1.1.0.M1 is available from https://repo.spring.io/milestone/.

What's new?

REST Assured

As an alternative to the lightweight server-less documentation generation offered by Spring Framework's MockMvc, you can now use REST Assured to test and document your RESTful services. This opens up Spring REST Docs to all four corners of the JVM and beyond, allowing you to document anything that you can access via HTTP.

Markdown

Support has been added for generating Markdown snippets. On its own, Markdown isn't as capable as Asciidoctor, but can work very well when combined with existing documentation toolchains such as Slate…

Entering Reactive Streams Era

Reactor 2.0 development started by the end of 2014, around the same time as Reactive Streams. We were keen on joining the effort and early adopt a backpressure protocol to mitigate our main message-passing limitation: bounded capacity. We delivered in Reactor 2.0 the first attempt to make Reactive Streams implementations of RingBuffer-based schedulers and derived an increasingly popular reactive pattern: Reactive Extensions.

Meanwhile, Reactive Streams started getting traction and an entire ecosystem of libraries discussed this transition. The regular concern ? Implementing Reactive Streams semantics is all but an easy task. We observed an increasing need for a reactive foundation to solve message-passing and implement common streaming operators. We therefore created a dedicated project space for Reactor Core and started a focused effort with Spring Framework team…

On behalf of the Spring Data team I'm happy to announce the first milestone of the Hopper release train. The release ships 250 tickets fixed! The most important new features are:

• Upgrade to Querydsl 4.
• Integration of Spring Data Neo4j 4.1, Spring Data Couchbase 2.1 and Spring Data Solr 2 (on Solr 5).
• Support for Redis Cluster.
• Support for projections on repository query methods in JPA and MongoDB (see the example for details).
• Addition of Spring Data Envers to the release train (previously maintained separately).

Find a curated changelog in our release train wiki or skim through a full list of changes in JIRA. We're shooting for a release candidate early March and a GA release at the…

On behalf of the community, I'm pleased to announce the release of Spring Session 1.1.0.RC1. The release can be found in the Spring Milestone Repository (https://repo.spring.io/milestone/).

This release contains lots of fixes and new features. You can find details in the What's New in 1.1 The highlights of 1.1.0.RC1 have been included below:

• Support for GemFire Thanks to John Blum!
• Allow writing to Redis immediately (instead of lazily) using redisFlushMode

We look forward to your feedback and if all goes well plan to release 1.1.0.RELEASE in the next few weeks.

Site | Documentation | Issues | …

On behalf of the team, I am pleased to announce the release of Spring Cloud Stream 1.0.0.M4. The new release comes with a few major changes and enhancements, and it defines core abstractions and primitives that we believe to be essential for the development of distributed real-time data processing applications. To name some of them:

Default publish-subscribe semantics

The most important change in Spring Cloud Stream 1.0.0.M4 is the way in which applications interact with each other. We have opted for a default publish-subscribe model, in which each application that receives messages from a given destination will receive a copy of the message. This is a better fit for the processing model of stream applications, where intermediate topics act as data hubs for the various intersecting data streams, also making scenarios such as tapping easier and more efficient. This feature goes hand in hand with the next, which is consumer groups…

We’re pleased to announce a first milestone release of Spring Statemachine 1.1.0.M1.

We released 1.0.0.M1 April 2015 and 1.0.0.RELEASE October 2015. We've also done 2 maintenance releases for 1.0.x series and now it's time to look in a future with a 1.1.x serie. 1.0.x enters into a maintenance mode while main development will focus on 1.1.x. This doesn't mean that we'll stop with 1.0.x, maintenance fixes for it will be done until we're succesfully transitioned beyond 1.1.x release. It is important in Spring projects to not drop maintenance until users are ready to move on into next minor/major…

Spring IO Platform 2.0.2.RELEASE is now available from both repo.spring.io and Maven Central.

This maintenance release upgrades the versions of a number of the projects in the Platform to pick up their latest maintenance releases:

• Spring AMQP 1.5.3.RELEASE
• Spring Boot 1.3.2.RELEASE
• Spring Integration Java DSL 1.1.2.RELEASE

The versions of several third-party dependencies have also been updated.

Project Page | GitHub | Issues | Documentation

Dear Spring Community,

The Spring Integration Java DSL 1.1.2 has been released and is available now from repo.spring.io and Maven Central.

This maintenance release includes several fixes and 3rd party dependency updates.

Thank you everyone for contribution and any kind of feedback!

We don't have particular plans for version 1.2, because we are looking into the absorption of Java DSL project by the Spring Integration 5.0, where Java 8 is minimal, but feel free to ask us for more features and share any concerns which can be considered to be included in the next maintenance release.

Project Page | JIRA | [Contributions] (https://github.com/spring-projects/spring-integration/blob/master/CONTRIBUTING.md) | StackOverflow (spring-integration…

Today we are pleased to introduce a new project in the Spring portfolio, Spring Cloud Task. Under the umbrella of the Spring Cloud grouping of projects and the sister project of Spring Cloud Stream, Spring Cloud Task aims to bring functionality required to support short lived microservices to Spring Boot based applications. With this blog post, we are releasing our first milestone of the project and are eager for your input and feedback.

The Goals of Spring Cloud Task

In most cases, the modern cloud environment is designed around the execution of processes that are not expected to end (think web applications or stream modules). If they do, it's considered a failure by the platform and they are typically restarted. While many platforms do have some method to execute a process that is expected to end (a batch job for example), the results of that execution are typically not maintained in a consumable way. Yet for mission critical applications, even though they are short lived, they still have the same non-functional requirements long lived processes have.

While this functionality is useful in a cloud environment, the same issues can arise in a traditional deployment model as well. When executing Spring Boot applications via a scheduler like cron, it can be useful to be able to monitor the results of the application after it’s completion.

A Spring Cloud Task takes the approach that a Spring Boot application can have a start and an end and still be production grade. Batch applications are just one example of where short lived processes can be helpful.

Getting Started

In this first release of Spring Cloud Task, we introduce the basics of the configuration mechanisms as well as a repository to record what happens when a task is executed. Those who are familiar with Spring Batch and its job repository should find the general paradigms of Spring Cloud Task familiar.

To get familiar with Spring Cloud Task, the easiest way is to write an application. The documentation walks you through the creation of an initial task and its execution. You can read more about that here.

Where we're going

Tasks will be a new primitive within Spring Cloud Data Flow in the coming releases allowing users to execute virtually any Spring Boot application as a short lived task. This provides the flexibility to run everything from a simple CommandLineRunner to a full batch job in dynamic way, allowing resources to be consumed on demand and returned once complete. The upcoming releases including Spring Cloud Task 1.0 GA which we plan for just before Spring Cloud Data Flow goes 1.0 GA, will be adding features to support that effort.

Tell us what you think!

Spring Cloud Task is a new and exciting project that we feel fills an under served area of enterprise development. However, we want to know what you think. Please let us know via the issues in Github Issues, StackOverflow, or directly on Twitter!