Most importantly, Spring Framework 4.3.x and therefore Spring Framework 4 overall will reach its end-of-life next year: Our EOL cut-off is December 31st, 2020, with no further support on 4.3.x beyond that point. At the same time, we are also phasing out 5.0.x and 5.1.x for good.
As for planned releases, first up is a full round in mid January: with 5.2.3 and 5.1.13 accompanied by 5.0.16 and 4.3.26. The latter are the last…
Today it’s my pleasure to announce General Availability of Spring Integration for Amazon Web Services extension version 2.3.0 and Spring Cloud Stream Binder for AWS Kinesis version 2.0.0.
These releases can be downloaded from Maven Central, JCenter, and our release repository:
The main theme of both these releases is about an integration testing using a Local Stack framework which helped us to spot several bugs and race conditions in both libraries.
The spring-integration-aws provides a PutRecordsRequest (batch) support for KplMessageHandler collecting async results for UserRecords in that batch using Project Reactor Mono.fromFuture() functionality.
A KinesisShardEndedEvent is now emitted from the KinesisMessageDrivenChannelAdapter when the next shard request returns null with the meaning that shard is closed and no records can be added to that any more.
The spring-cloud-stream-binder-kinesis is based on the recently released Spring Cloud Stream version 3.0 and provides a new KinesisBinderHealthIndicator to check that all the streams involved in binding configurations are available.
We are pleased to announce the general availability of Spring Cloud Open Service Broker 3.1.0.RELEASE. Support for Open Service Broker API v2.15 is now feature complete. Thanks to the community for your feedback and contributions! This release includes all of the fixes and enhancements from the pre-release milestones:
Upgrade to Spring Boot 2.2.1.RELEASE
Add ServiceBrokerMaintenanceInfoConflictException to handle MaintenanceInfoConflict error scenarios
ServiceBrokerInvalidParametersException now returns an HTTP 400 when a create or update request is malformed or includes invalid parameters. Previously it was, incorrectly, returning an HTTP 422.
CreateServiceInstanceBindingRequest now extends AsyncParameterizedServiceInstanceRequest in order to utilize a common request object and reduce redundancy.
I am happy to announce the 4.4.2 release of the Spring Tools 4 for Eclipse, Visual Studio Code, and Theia.
Highlights from this release include:
(Spring Boot), (Eclipse) enhancement: new actions to connect/refresh/disconnect live hover information for running Spring Boot projects now available from the Boot Dashboard menus (context-menu + view toolbar)
(Spring Boot), (Eclipse) enhancement: Optional link console tab with Boot Dashboard selection (#386)
(Spring Boot), (VSCode): early version of more detailed progress reporting for live hover information mechanism
On behalf of the community, I'm pleased to announce the availability of the Spring Data Moore SR2 and Lovelace SR13 service releases.
Both releases fix 66 tickets in total, mostly bugfixes. We decided to ship both versions on short notice to address bugs around auditing and converter registration for a broader range of users, as we've noted an increased number of bug reports in both areas. If you use Spring Data through Spring Boot, you can consume the released artifacts by setting the spring-data-releasetrain.version property to Moore-SR2 or Lovelace-SR13.
I’m pleased to announce the releases of Spring Security OAuth 2.4.0 and 2.3.8.
Deprecation Notice
The 2.4.0 release officially deprecates all classes. The latest OAuth 2.0 support is provided by Spring Security. See the announcement for further details.
We are pleased to announce the 3.1.0.RC1 release of Spring Cloud Open Service Broker. Support for Open Service Broker API v2.15 is now feature complete, and we expect for this to be the final milestone before a GA release. Thanks to the community for your feedback and contributions! This release includes the following fixes and enhancements:
Upgrade to Spring Boot 2.2.1.RELEASE
Add ServiceBrokerMaintenanceInfoConflictException to handle MaintenanceInfoConflict error scenarios.
ServiceBrokerInvalidParametersException now returns an HTTP 400 when a create or update request is malformed or includes invalid parameters. Previously it was, incorrectly, returning an HTTP 422.
CreateServiceInstanceBindingRequest now extends AsyncParameterizedServiceInstanceRequest in order to utilize a common request object and reduce redundancy.
