Dear Spring Community,
I am happy to announce the 4.2.2 release of the Spring Tools 4 for Eclipse, Visual Studio Code, and Atom.
Highlights from this release include:
- (all language servers) performance: additional improvements to language server startup time
- (Spring Boot) new: navigation for bean identifiers, bean classes, and property names for Spring XML config files
- (Spring Boot) new: content-assist rolled out for many more Spring XML config elements and attributes
- (Spring Boot) fixed: Detect @RequestMapping with path defined as constant instead of literal string (#281)
- (CF Manifest) new: added support for anchors and references
- (Eclipse) new: added project-related XSD schema resolution
- (Eclipse) fixed: high CPU and memory spikes when code minings and live hovers are active (#292)
The Spring Cloud Data Flow team is pleased to announce the release of 2.1 of Data Flow.
We have a brand new website with great new content, which is where you can find our getting started guide for use on Cloud Foundry and Kubernetes and your Local Machine.
Here are the highlights:
New Dedicated Data Flow Website
The Data Flow team takes pride is openly communicating with the community in various forums including StackOverflow, Gitter, GitHub, Twitter, and at times in Email and Zoom calls even.
However, we realized that we could provide a much better experience to answer common questions and provide an easier on-ramp to using Data Flow if we focused on improving the online documentation. The reference guide was not the ideal format to achieve that goal, so we embarked on creating a new website - https://dataflow.spring.io - that acts as the hub for learning about all things Data Flow related.
Hi Spring fans! It’s been quite a crazy week! I was in Spring I/O last week in Barcelona, Spain and there was a deluge of interesting news to come out of the show! I loved the show - a sort of mini SpringOne - and am chomping at the bit to see what comes next. I’m now beginning a small tour starting in Zurich, Switzerland; then I’m off to the paradise-like Paris, France for the epic SpringOne Tour event there, then I’m off to Minsk, Belarus; then off to Barcelona, Spain for JBCN, and then - finally - home for the middle school graduation of my kid at the end of the month. So much exciting stuff culminating in an even more exciting event, I can hardly stand it!
Josh Long often says that “production is the best place on the Internet.” But where I used to work, developers needed to negotiate with operations, networks, and security before their code could go anywhere near this promised land.
Understandably, each of these disciplines seemed to have the same hidden agenda: change is bad. Experience had taught us that change was difficult and error-prone, so as a company we’d become risk-averse and cautious about our deployments. Releases were infrequent and large. There was plenty that could go wrong.
HI Spring fans! In this installment Josh Long (@starbuxman) talks to Nicolas Frankel (@nicolas_frankel) about integration testing, blogging, Kotlin, application security, living on the French/Swiss border, blogging consistently, and much more. It’s an interview with one of my favorite voices in the community.
Back in 2016, our reactive journey started with Spring Framework 5 accompanied by a couple of reactive integrations. Throughout our journey, other projects joined the reactive movement. With R2DBC, we now also provide a reactive integration for SQL databases. With the growth of transaction-capable integrations, we constantly got asked:
At the time our journey began, we had no reactive form of transactional integrations, so this question was simple to answer: There’s no need for reactive transaction management.
The 4th Generation of Reactor is arriving. On behalf of the team we want to thank all our community for the tremendous feedback. Over the last year we have grown our reactive line-up significantly including R2DBC and BlockHound. Our adoption in the java ecosystem looks phenomenal and we are collaborating with major corps including Microsoft and Google. We have more than doubled our regular Gitter audience with some awesome -you guessed it- reactive discussions happening every day. Finally, Sergei Egorov has joined the core team and we have no plans to stop expanding!
The 8th Service Release for Californium is out. Beyond fixing its share of issues, it is shipping with a turbo-charged
reactor-netty -thanks to changes backported- from our new Dysprosium-M1 release.
The release is available on your preferred maven central repository.
Note that the release overrides
Californium-SR7 which has shipped with an unwelcome regression in
Anticipating the coming
Dysprosium-RELEASE, our reactor-core 3.1.x and reactor-netty 0.7.x lines will not receive further patches. We encourage our users to update to
Californium releases trains, which match Spring Boot 2.1.x and Spring Framework 5.1.x.