Dear Spring community,

I'm pleased to announce that Spring Framework 5.0.2 and 4.3.13 are available now, as a pair of refinement releases which are recommended as immediate upgrades for all Spring users. They will also be part of the upcoming Spring Boot 2.0 M7 and 1.5.9 releases, respectively.

5.0.2 comes with significant tightening-up across the framework, including performance improvements and fine-tuned configuration variants. Many of those changes have been backported to 4.3.13 for streamlined consumption in existing applications.

Please note: Our Castor XML support is marked as deprecated now due to the inactivity of the Castor project. On a related note, we are effectively deprecating JDK 6 support in the 4.3.x line, ending our first-class efforts for it; more on this in a separate blog post…

On behalf of the entire team, I’d like to announce the availability of Ingalls SR9 and Kay SR2 releases. We didn't announce Ingalls SR8 at the time we shipped it, apologies for that. The service releases ship over 90 issues fixed in total and are recommended upgrades for all users.

For your convenience the service releases are going to be picked up in the upcoming Spring Boot 1.5.9 release, and Kay SR2 will be part of Spring Boot 2.0 M7. You can find the complete list of issues fixed here for Ingalls SR9 and here for Kay SR2.

Spring Data Ingalls SR9

• Spring Data Commons 1.13.9 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data JPA 1.11.9 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Neo4j 4.2.9 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data KeyValue 1.2.9 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Gemfire 1.9.9 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data MongoDB 1.10.9 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data for Apache Cassandra 1.5.9 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data for Apache Solr 2.1.9 - Artifacts - JavaDocs - Documentation - …

On behalf of the team and community, I am pleased to announce that the General Availability (RELEASE) of the Spring Cloud Edgware Release Train is available today. The release can be found in Maven Central. You can check out the Edgware release notes for more information.

Notable Changes in the Edgware Release Train

Spring Cloud Bus

Updates to allow Bus clients to implement remote events in independent packages.

Spring Cloud Task

See the blog post announcing Task 1.2.0.

Spring Cloud Commons

Adds support for back off policy when retrying requests.

Spring Cloud Stream

See the Ditmars release announcement for more…

I am pleased to announce that the 1.1.0.RELEASE of Spring Integration for Amazon Web Services is now available in the Spring release repository and Maven Central.

First of all thanks to all community members for any feedback and contributions to make features in this project available!

Some highlights what we have after a year and a couple months of amazing team work:

• S3StreamingMessageSource to get access to S3 resources content on demand;

• KinesisMessageHandler and KinesisMessageDrivenChannelAdapter for interaction with AWS Kinesis service;

• DynamoDbMetaDataStore to store metadata in the AWS DymanoDB table;

• And, of course, a ton of bug fixes!

…

On behalf of the team, I am pleased to announce the release of Spring Cloud Skipper 1.0 M2.

Skipper is a lightweight tool that allows you to discover Spring Boot applications and manage their lifecycle on multiple Cloud Platforms. You can use Skipper standalone or integrate it with Continuous Integration pipelines to help implement the practice of Continuous Deployment.

The 1.0 M2 release fixes several bugs and introduces a few new features.

• Support for Postgres, MySQL, Microsoft SQL Server, and HSQLDB databases.
• Improved support for upgrading applications that use an HTTP location for the resource definition.
• LRU cache used to manage disk space for HTTP and Maven based resources that are downloaded.
• HTTP based resources are always downloaded, never cached.
• Use updated CF Deployer library with an HTTP based health check.
…

On behalf of the community, I’m pleased to announce the release of Spring Security OAuth 2.2.1.RELEASE.

The 2.2.1.RELEASE is a maintenance release that includes bug fixes and minor improvements.

Project Page | GitHub | Documentation | Help

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

Notable Changes in the Finchley Release Train

This update is primarily for interoperability with Spring Boot 2.0.0.M6.

The following modules were updated as part of Finchley.M4:

We are pleased to announce that Spring Cloud Task 2.0.0.M2 is now available to download from Spring’s milestone repository. Many thanks to all of those who contributed to the release.

This release brings Spring Boot 2.0 M5 compatibility. With this upgrade, all dependencies are also upgraded (Spring Cloud, Spring Cloud Stream, Spring Batch, etc).

What do you think?

We look forward to your feedback on Github, StackOverflow, Gitter

Spring Cloud Task Home | Source on GitHub | Reference Documentation

We are pleased to announce the first Release Candidate for the version 2.1 of the Spring for Apache Kafka:

repositories {
    maven { url 'http://repo.spring.io/milestone' }
}
compile "org.springframework.kafka:spring-kafka:2.1.0.RC1"

The general reason for so quick point release is the recently released Apache Kafka 1.0.0 version. There are no critical feature in that release, but some breaking changes in the kafka.admin and kafka.streams have been introduced. Therefore this release represents mostly compatibility with Apache Kafka 1.0.0:

• Deprecate bounce() and waitUntilSynced() in the KafkaEmbedded since respective API in the AdminUtils have been removed

• The KStreamBuilderFactoryBean now uses StreamsBuilder instead of deprecated KStreamBuilder

• The @EmbeddedKafka.brokerProperties() can be configured with the properties placeholders

• The SpEL expressions in the @KafkaListener attributes now can be used simplified since BeanFactory resolver is supplied with the TemplateAwareExpressionParser

• A NonResponsiveConsumerEvent has been introduced to track the sate of the ListenerContainer for possible target Broker unavailability

  …