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.
Hi Spring fans! Welcome to another installment of This Week in Spring! Can you beleive we're less than six weeks away from 2018? Time sure flies when you're having fun!
This week I'm in Los Angeles talking to community members and then taking in the Thanksgiving holiday here in the US surrounded by friends and family. Thanksgiving is a chance to reflect on that for which we are thankful. I am sure that I speak for all of us here on the Spring and Pivotal teams when I say that we are thankful for you. Thank you for making this the most amazing, dynamic, exhilarating and interesting community…
Hi Spring fans! Welcome to another installment of This Week in Spring! This week I am in Casablanca, Morocco for the amazing Devoxx Morocco event talking to developers in the hub of North Africa.
Can you believe it's already the middle of November? And can you believe we are less than a month away from the amazing SpringOne Platform event in San Francisco, CA? I hope you're going!
Now, without further ado, let's get to it.
Spring messaging ninja Oleg Zhurakousky just announced Spring Cloud Stream Elmhurst.M3 / 2.0.0.M3. The new release improves content-type resolution, support for Apache Kafka 0.11+, and introduces a good deal of nice samples.
Spring Data Geode/GemFire lead John Blum just announced Spring Data Geode / GemFire 2.0.0.RC1. The new release updates dependencies, builds on Java 8 (introducing Java 8 types and lambdas), and introduces new samples.
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).
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
We are pleased to announce the 2.0.0.M3 release of the Spring Cloud Stream Elmhurst release train.
Spring Cloud Stream Elmhurst 2.0.0.M3 is available for use in the Spring Milestone repository. The release notes include relevant information about version compatibility with Spring Boot, Spring Cloud, Spring AMQP, and Spring for Apache Kafka.
The following sections list new features and improvements included in this release:
Improved Content Type Resolution
The content-type resolution has been improved and consolidated in the channel interceptors, which makes it configurable for situations that require application-level customizations. Also, based on the community feedback, we now set the default content-type as application/json. However, it is still possible to override it via BindingProperties or it can be passed with the Message…