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

Include the following Spring Boot starter:

…

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.

Spring Cloud Config

…

Dear Spring Community,

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

Highlights from this release include:

• (Eclipse Theia vs Atom) Eclipse Theia now officially supported, Atom support deprecated
• (Spring Boot) improvement: project classpath notifications now happen in batch on startup to further optimize performance and job load on the Eclipse side
• (Spring Boot) improvement: symbols are now being re-created if dependent types change
• (Spring Boot) fixed: Slow code completion takes more than a 1 sec. (#293)
• (Spring Boot) fixed: content-assist for Spring XML config files now working again in VS Code and Theia
• (Spring Boot) fixed: Anonymous inner type beans don't have boot hints
• (CF Manifest)…

Dear Spring Community,

I am happy to announce the 3.9.9 maintenance release of the Spring Tool Suite 3 (STS3).

Highlights from this release include:

• updated to Eclipse 2019-06 release
• mimics the https-preferring XSD schema lookup of the core Spring framework
• allows users to use https for Spring schema locations as default
• various bug fixes

To download the distributions, please go visit:

• Spring Tool Suite 3: https://spring.io/tools3/sts/all
• Detailed new and noteworthy notes can be found here: STS 3.9.9 New & Noteworthy.

STS 3.9.9 is presumably the final release of the Spring Tool Suite 3 distribution. At the moment, there are no further updates or maintenance releases planned. For moving forward we recommend to switch to the next generation of the tooling, the Spring Tools 4. In case of high demand, we might produce additional maintenance update releases of the Spring Tool Suite 3. But in case you are missing important features in the new Spring Tools 4 that prevents you from switching over, let us know and report an enhancement request at https://github.com/spring-projects/sts4/issues…

On behalf of the Java CFEnv community I am happy to announce the release of Java CFEnv 1.1 GA.

This release add support for the following services:

• Volume Services

• Pivotal Single Sign-On Service

• Pivotal Redis Service

It also adds the following functionality:

• Checks the classpath to correctly determine setting of MySQL or MariaDB driver class name.

• When using the Spring Boot support, an exception is thrown if the Spring Cloud Connector library is on the classpath. This applies only for the following services: DataSource, RabbitMQ, Cassandra, MongoDB, and Redis. The exception message indicates to set the environment variable JBP_CONFIG_SPRING_AUTO_RECONFIGURATION '{enabled: false}'

• Support for Boot 1.5.x by copying a logging utility class into the project.

…

On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Boot 2.1.6 has been released and is now available from repo.spring.io and Maven Central.

This is a maintenance release that includes a number bug fixes, dependency updates and documentation improvements.

Remember that Spring Boot 1.5 will be end of life in august, so all users should now be upgrading to Spring Boot 2.1.

How can you help?

If you're interested in helping out, check out the "ideal for contribution" tag in the issue repository. If you have general questions, please ask on stackoverflow.com using the spring-boot tag or chat with the community on Gitter…

On behalf of the team and everyone that contributed, I am pleased to announce that the fourth milestone of Spring Boot 2.2 has been released and is available from our milestone repository. This release closes over 170 issues and pull requests.

For a complete list of changes and upgrade instructions, please see the Spring Boot 2.2 Release Notes on the wiki and the updated reference documentation.

If you want to get started with 2.2 and try out the new features, you can bootstrap a new project on https://start.spring.io.

Project Page | GitHub | Issues | Documentation | Stack Overflow | Gitter

We have released Spring Security 4.2.13 to address CVE-2019-11272: PlaintextPasswordEncoder authenticates encoded passwords that are null.

Users are encouraged to update immediately.

With Spring Boot, you can override the Spring Security version in Maven like so:

<properties>
    <spring-security.version>4.2.13.RELEASE</spring-security.version>
</properties>

Or in Gradle like so:

ext['spring-security.version'] = '4.2.13.RELEASE'

Note that users of Spring Security 5+ are not affected by this vulnerability.

On behalf of the Spring and Apache Geode communities, it is my pleasure to announce the release of Spring Boot for Apache Geode & Pivotal GemFire (SBDG) 1.0.1.RELEASE and 1.1.0.M2.

New in SBDG 1.0.1.RELEASE

SBDG 1.0.1.RELEASE builds on:

• Spring Framework 5.0.14.RELEASE

• Spring Boot 2.0.9.RELEASE

• Spring Data Kay-SR14

• Spring Session for Apache Geode & Pivotal GemFire 2.0.9.RELEASE

Additionally, SBDG now supports the ability configure and bootstrap a Locator process, which disables the auto-configuration supplying a ClientCache instance, by default.

See the complete changelog for further…