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

  …

On behalf of the team, it is my pleasure to announce that Spring Boot 2.0.0.M6 has been released and is now available from our milestone repository. This release closes 141 issues and pull requests and continues our progress towards 2.0 GA. Thanks to everyone that has contributed!

This milestone refines a number of items from previous milestones, and provides a number of notable new features:

• Initial support for HTTP/2 - At the moment Tomcat and Undertow are supported (See #10902 for the Jetty support)
• Improved support for WebFlux-based apps - Spring Boot now supports TLS configuration for all containers and error page support is available
• Kotlin extension - The first Kotlin extension has landed. You can now start your app in a more idiomatic way:
…

We are pleased to announce that Spring Batch 4.0.0.RC1 is now available via Github and the Pivotal download repository. This release represents the first release candidate for the Spring Batch 4.0 release. Many thanks to all that contributed to this release.

What's new?

This release represents the completion of new functionality work on the 4.0.0 line. New features in Spring Batch 4 include:

• Updated baseline
• New builder APIs for out of the box components
• Updated, java configuration friendly, documentation

Updated Baseline

Spring Batch 4.0 is taking the opportunity to reset the baseline…

On behalf of the community, I’m pleased to announce the release of Spring Security 5.0.0.RC1. This release resolves 150+ issues. Below are the highlights of this release:

• WebFlux Security Highlights

  • ReactiveSecurityContextHolder

  • Reactive CSRF Support added

• OAuth 2.0 Highlights

  • OAuth 2.0 Client Support

  • OAuth2AuthorizedClient / Service

  • What’s Up Next with OAuth 2.0 Support?

• Core Highlights

  • Password Storage Updated

  • Add UnboundId LDAP inmemory support

  • Allow use of non-numeric (e.g. UUID) values for ObjectIdentity.getIdentifier()

ReactiveSecurityContextHolder

Previously, Spring Security used the ServerWebExchange.getPrincipal() as the source of truth for who was authenticated. The authenticated user was copied to Reactor’s Context to support method security which used the Reactor Context as it’s source of…

On behalf of the community I’m pleased to announce the release of Spring Session 2.0.0.RC1. This release puts some final touches to preparing for 2.0.0.RELEASE. You can find the complete changelog in github, with the highlights below:

• #906 Simplified integration with the Servlet APIs. With this simplification, we have removed the support for supporting multiple sessions for a single user. We plan on looking into other ways to bring this feature back.

• #907 Support for configuring Redis session cleanup cron

Project Site | Reference | Help

On behalf of the Spring Integration team I am pleased to announce that the Release Candidate 1 for the Spring Integration 5.0 version (5.0.0.RC1) is now available.

It can be downloaded from the Milestone Repository:

repositories {
    maven { url 'http://repo.spring.io/libs-milestone' }
}

compile "org.springframework.integration:spring-integration-core:5.0.0.RC1"

20 JIRAs (and some GitHub issues) are included in this release, together with bug fixes and a number of new features. Some highlights of features in the RC1, since the previously announced Milestone 7:

• The components populated by the Java DSL parser are now registered as BeanDefinitions in the application context, thanks to newly introduced in the Spring Framework 5.0 Supplier-based programmatic bean registration. This approach helps us to avoid some boilerplate code for singletons registration and initialization. In addition this BeanDefinition registration may be useful in some use-case to select particular components in the application context. In fact, exactly that is used in the Spring Cloud Function project for java.util.function.* beans scanning.

• The IntegrationFlows.from(Class<?> serviceInterface) has now overloaded version with an additional beanName argument. This becomes exactly the bean name for a generates gateway proxy overriding the [flowId].gateway value:

  @Bean public IntegrationFlow uppercaseFlow() { return IntegrationFlows.from(MessageFunction.class, "uppercase") .<String, String>transform(String::toUpperCase) .get(); }

  …