Dear Spring Community,

I am happy to announce the 3.8.2 release of the Spring Tool Suite, our Eclipse-based tooling.

STS 3.8.2 focuses on adopting Eclipse Neon.1 and fixing existing issues. The list of changes include:

• Updated to Eclipse Neon.1
• Includes Eclipse Automatic Error Reporting
• Custom Spring Initializr now usable directly from within STS
• New Spring Starter Wizard now features default selections
• Fixed a problem that caused parallel push of multiple apps in boot dashboard to fail
• Fixed a deadlock when selecting BuildShip in New Spring Starter wizard
• and more...

To download the distributions, please go visit:

• Spring Tool Suite: https://spring.io/tools/sts/all

Detailed new and noteworthy notes can be found here: STS 3.8.2 New & Noteworthy.

Enjoy!

Spring Cloud Data Flow for Cloud Foundry gets two new releases today, detailed below:

1.0.1.GA is a maintenance release that

• Builds upon 2.0.1.RELEASE of Cloud Foundry’s Java Client and 3.0.2.RELEASE of Reactor

• Builds upon 1.0.1.RELEASE of Spring Cloud Data Flow core

• Gets general clarifications and improvements in the reference documentation

• Fixes a bug pertaining to multiple ORG + Space combination causing task launch failures

• Fixes a bug where environment variables were not propagated correctly when launching a task

1.1.0.M1 is the first milestone in the new line of development…

On behalf of the community, I am pleased to announce the release of Spring LDAP 2.2.0.RC1.

What’s New in Spring LDAP 2.2

You can find highlights of what’s new in the What’s New in Spring LDAP 2.2 section of the reference.

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.

Feedback Please

If you have feedback on this release, I encourage you to reach out via StackOverflow, GitHub Issues, or via the comments section. You can also ping me @rob_winch or Joe @joe_grandja on Twitter.

Of course the best feedback comes in the form of contributions…

Spring Integration 4.3.4 and 4.2.11 are now available, as well as Spring AMQP 1.6.3.

These include some important bug fixes and all users are encouraged to upgrade. Click on the release links above to see closed issues.

See the project pages for documentation, download information etc.

• Spring Integration Project Page

• Spring AMQP Project Page

On behalf of the team, I am pleased to announce the release of the first milestone of Spring Cloud Data Flow for Kubernetes 1.1 along with a 1.0.1 maintenance release.

Spring Cloud Data Flow for Kubernetes provides support for orchestrating long-running (streaming) and short-lived (task/batch) data microservices on Kubernetes.

Note: A great way to start using this new release(s) is to follow the release matrix on the project page, which includes the download coordinates and the links to the reference guide.

The most significant change for both of these releases is the way we handle task launching. We used to orchestrate them as a Job with associated Pods, but that proved problematic in terms of failed jobs getting restarted even with a RestartPolicy specified as "Never". To resolve this, we now launch the tasks using bare pods…

On behalf of the entire team I'd like to announce the availability of two service releases for Spring Data release trains: Hopper SR4 and Gosling SR6. The releases are recommended upgrades as they contain fixes for a CVE in Spring Data JPA.

Spring Boot 1.3.8 and 1.4.1 users got Hopper SR3 and Gosling SR5 shipped out of the box. Those releases also already contain the fixes for CVE but unfortunately broke Java 6 compatibility. To re-instantiate the latter, please upgrade to the latest ones by setting the spring-data-releasetrain.version property to the corresponding value. Non-Boot users can just upgrade to the new BOM. As usual, the next Spring Boot releases will pick up the improved fixes as part of…

We’re pleased to announce a first milestone release of Spring Statemachine 1.2.0.M1. Artifacts are available from Spring Repository.

What we got into this first milestone:

• Usual bug fixes and small enhancements
• Support for UML submachines
• New Repository abstraction keeping machine configuration in an external repository
• New support for state actions.
• New transition error action concepts

There has been a support for complex state hierarchy from a day one but trouble was that everything had to be defined in a same state configuration. New submachine support adds a feature where a state can be…

Dear Spring Community,

I’m pleased to announce that the Java DSL for Spring Integration 1.2 RC1 is available now.

Since the previous Milestone 2 we had a good deep feedback for our new features and some API has been broken to reflect real requirements.

As usual, big thanks to everyone who created issues, raised Pull Requests, provided feedback or just asked questions on StackOverflow.

The artifact org.springframework.integration:spring-integration-java-dsl:1.2.0.RC1 is available in the Milestone repo. So, give it a shot for last chance to raise a GH issue for any feedback!

Now about the changes in the 1.2 RC1…

After more than a year of work, multiple milestones and fine tuning based on much feedback, I have the pleasure of announcing Reactor 3 General Availability. You will find Reactor Core 3.0.2.RELEASE on Maven Central.

What is Reactor 3 ?

Reactor 3 provides a powerful and efficient reactive programming model for Java 8 based applications. The model builds upon the experience of both Reactor 2 and RxJava 1 and introduces a fluent way to compose asynchronous backpressure-ready event processing. Spring Framework 5 uses Reactor 3 to build and eventually expose a complete reactive story.

Its design relies on an extensible execution model that favors event processing colocation. Typically, Reactor will be jumping threads between event flow stages only when explicitly asked so. For instance, in-memory operations such as list access or payload transformation do not usually require a thread boundary. If the operation producer or receiver might take time, users are expected to operate their flow with Flux#publishOn / Mono#publishOn or Flux#subscribeOn / Mono#subscribeOn and choose a Scheduler to run on. Alternatively, if a user is combining the results of many Publisher as with …