The Spring Blog

News and Events

Spring Cloud Data Flow 2.2.0 Released

The Spring Cloud Data Flow team is pleased to announce the GA release of 2.2.0.

In this GA release, Spring Cloud Data Flow team has worked on some of the key features including task application management, stability on the product by increasing the acceptance tests coverage across platforms (local, Kubernetes and Cloud Foundry), bug fixes and enhancements.

Task Application Management

It is now possible to stop and delete task executions using the SCDF Dashboard and the Shell.
We have added support for task application monitoring using micrometer integration. The core of the Micrometer integration landed in Spring Cloud Task’s 2.2.0 release-line, which by the way is a requirement if you are going to try out the Task-metrics and the SCDF integration.


Simplifying the Spring Cloud Release Train

Spring Cloud continues to prove immensely popular, and over the last few years a number of IaaS providers have provided integration with their technology and joined the release train. This has typically involved getting into the spring-cloud GitHub org and publishing in the Maven groupid. As the number of projects included looks to increase, it is becoming a little unwieldy, and we wanted to take a step back and review the pros and cons that this model provides and propose a better path forward that benefits all projects involved.


Spring Tools 4.3.1 released

Dear Spring Community,

I am happy to announce the 4.3.1 release of the Spring Tools 4 for Eclipse, Visual Studio Code, and Theia.

Highlights from this release include:

  • (all language servers) performance: further improvements to the language server startup time
  • (Spring Boot) fixed: wrong error markers in properties files (#314)
  • (VS Code) fixed: vscode goto definition error with lsp (#309)
  • (Eclipse) fixed: STS4 can now be installed again into an existing Eclipse install when running on JDK8
  • (Eclipse) fixed: deadlock when starting up the Spring Boot language server for workspaces with many projects
  • (Eclipse) fixed: cannot launch apps in boot dashboard anymore when using early builds of Eclipse 2019-09 (4.13)
  • (Eclipse) improved, but not completely fixed yet: freeze when opening pom.xml file - if you still experience slowness here, please apply the workaround as documented in the issues comment (comment on #314)

Explore the project on

Introducing the new feature on Explore the project.
With this, you can now take a peek at the generated project files without having to actually download it, unzip it, etc.

A lot of developers requested this feature, because they’d like to compare with another project, or upgrade an existing application. We’d like to explore those possibilities more in the future, so send your feedback our way!

Explore the project:

  • Depending on the project, the pom.xml / build.gradle / build.gradle.kts will be shown by default
  • Highlighting code (1), preview markdown
  • Copy and download a file

Spring Cloud Hoxton.M1 is available.

On behalf of the community, I am pleased to announce that Milestone 1 (M1) of the Spring Cloud Hoxton Release Train is available today. The release can be found in Spring Milestone repository. You can check out the Hoxton release notes for more information.

Notable Changes in the Hoxton Release Train

This milestone release is compatible with Spring Boot 2.2.0.M4.

Spring Cloud Gateway

Spring Cloud Gateway has added support for RSocket. Look for more in an upcoming blog post.

Spring Cloud Contract

Gradle support has been updated to 5.5, and Groovy to version 2.5. A major refactoring has happened, simplifying and rewriting to Java where possible.


Spring Boot for Apache Geode & Pivotal GemFire 1.1.0.M3 Released!

On behalf of the Spring, Apache Geode and Pivotal communities, I am pleased to announce the release of Spring Boot for Apache Geode & Pivotal GemFire 1.1.0.M3.

What’s New

The main theme of this release was to add support for hybrid cloud deployments.

For instance, perhaps you want to push and run your Spring Boot, Apache Geode or Pivotal GemFire applications on Pivotal CloudFoundry (PCF), but connect those applications to an externally managed, standalone Apache Geode or Pivotal GemFire cluster. Now, SBDG allows you to do just that.

Technically, SBDG takes advantage of a feature in PCF called CUPS, or Create User-Provided Service. By defining your own service descriptor you can connect your Spring Boot applications to externally managed services, like databases, message queues and even In-Memory Data Grids & Caches like Apache Geode or Pivotal GemFire.

By following a prescribed service descriptor format, it makes it simple to switch to a platform managed service like Pivotal Cloud Cache when you need it.

Indeed, we believe this is an important stepping stone for users making their way to a Cloud-Native platform, like PCF, where they still have much invested in their legacy architectures.

We do highly recommend using a managed service like Pivotal Cloud Cache for your application and Microservices caching needs, but we also realize that making this switch is not as easy as flipping the switch.

We want to help you get there. After all, Cloud-Native (Data) Patterns are crucial to the modern application architecture, particularly when talking about things like high availability and resiliency as well as making effective use of your computing resources.

You can learn more about this new support in the Reference Documentation.

In addition to hybrid cloud support, we also added:

  • Auto-configuration for logging.

  • Support to target specific Pivotal Cloud Cache (PCC) service instances when multiple instances are bound to your Spring Boot app.

  • Upgrades to Spring Boot 2.1.6.RELEASE.

  • Upgrade to Spring Test for Apache Geode & Pivotal GemFire (STDG) 0.0.5.RELEASE.

See the changelog for more details.


Spring Cloud Open Service Broker 3.1.0.M1 Released

We are pleased to announce the 3.1.0.M1 release of Spring Cloud Open Service Broker. We are planning to include support for the recently released Open Service Broker API v2.15 within 3.1.0. This release includes all of the latest fixes and improvements from 3.0.3.RELEASE, as well as the following enhancements:

  • Improve support for service metadata in configuration properties
  • Add support for configuring Base64 metadata.imageUrl data from a class path image file
  • Improve configuration of event hooks via additional bean and auto-configuration support

Spring Cloud Open Service Broker 3.0.3 Released

We are pleased to announce the 3.0.3 release of Spring Cloud Open Service Broker. This release includes the following updates:

  • Upgrade to Spring Boot 2.1.6.RELEASE
  • Fix issue with Servlet API and Reactor transitive dependencies
  • Return 404 when attempting to request a service instance binding for a service instance that does not exist

Include the following Spring Boot starter:


Spring Cloud Greenwich.SR2 is available.

On behalf of the community, I am pleased to announce that Service Release 2 (SR2) of the Spring Cloud Greenwich Release Train is available today. The release can be found in Maven Central. You can check out the Greenwich release notes for more information.

Notable Changes in the Greenwich Release Train

All projects were updated in coordination with the Spring nohttp effort.

Spring Cloud Gateway

Many updates and fixes were included via Reactor and Reactor Netty. Gateway also efficiently caches the request body when Retry is enabled or if the Read Body Predicate is used.