Spring Team
Simon Baslé

Simon Baslé

Project Reactor Committer

Paris, France

Blog Posts by Simon Baslé

Announcing Reactor Bismuth-SR10

On behalf of the Reactor team, I have the pleasure of announcing a first shipment of Reactor goodness this week: Reactor Bismuth-SR10 is out 🚢

Stay tuned for a Reactor Californium milestone later this week 🕵🏻‍♂️

Reactor Bismuth-SR10

The latest maintenance BOM of the 3.1.x line, Bismuth-SR10, is out. It includes two new artifacts (click on the version numbers to see the release notes on GitHub):

One update considerations though: Flux.last() used to skip throwing a NoSuchElementException on some category of empty sources (Flux or Mono that are Callable, like Flux.empty()). This is a bug and it correctly does throw now.

Read more...

Reactor BISMUTH-SR7 is out!

On behalf of the whole Reactor Team, it is my pleasure to announce that the Reactor BISMUTH-SR7 release train is now available. As always, we recommend using the reactor-bom Bill Of Material.

In time for Spring Boot 2, this release train comes with improvements and bugfixes to core, extras, and reactor-netty.

This blog post highlights the most significant changes in both SR7 and last week’s SR6 release trains.

Reactor-Core 3.1.5

What’s new since 3.1.3? See the full release notes of the 3.1.4.RELEASE and the 3.1.5.RELEASE. Core changes include more than 15 improvements and bugfixes.

Read more...

Sneak peek at Reactor-Core 3.2 with Milestone 1

Greetings Reactive Spring community!

While the team is still working heavily on the 3.1 line, we also wanted to give the community a chance to get a sneak peek at what’s coming for the future 3.2 line.

In particular, the big goodie slated for 3.2.0.RELEASE is the addition of what we’ve been calling "error mode", "continue mode" or lately more officially "error strategy".

The idea

It is simple, really: what if exceptions in user code that get executed within operators could be recovered from, allowing the sequence to continue?

Read more...

Reactor Bismuth is out

It is my great pleasure to announce the GA release of Reactor Bismuth, which notably encompasses reactor-core 3.1.0.RELEASE and reactor-netty 0.7.0.RELEASE 🎉

With the release of Spring Framework 5.0 now just happening, you can imagine this is a giant step for Project Reactor :)

bismuth crystal
Like the bismuth crystal this release is intricate

 
The release contains a lot of changes and API polishing. For reactor-core you can find the exhaustive list in the release notes.

Important
There is a known (minor) issue with the reactor-core and reactor-test sources jars: They contain duplicate java source entries. See issue #887 for more details.
Read more...

Announcing First Release Candidate of Reactor Core 3.1

On behalf of the Reactor team, it is my pleasure to announce that reactor-core 3.1.0.RC1 has been released 🎉. This is a big last step towards GA release of 3.1 at the end of the month, the long term support version that will back Spring 5!

It is also complemented by various releases, all tied together in the Bismuth-M4 Release Train and BOM:

  • reactor-test, reactor-extra, reactor-adapter and reactor-logback all made the cut to 3.1.0.RC1
  • reactor-netty has seen significant updates and bug fixes in the new 0.7.0.M2 milestone
  • reactor-kafka has been released in its 1.0.0.M4 milestone
Read more...

Reactor Bismuth release train first milestone available

On behalf of the Reactor team, it is my pleasure to announce that Reactor hit an important milestone last week, making the Bismuth-M1 release train available.

This first milestone backs the newly released Spring Framework 5 RC1. It notably includes version 3.1.0.M1 of reactor-core, reactor-test and reactor-extra.

As the 3.1.x generation is slated to be the long term support branch (as is appropriate for a version that backs the Spring framework), focus has been on stabilizing and polishing the API. As such, expect some breaking changes from the 3.0.x versions [1].

Read more...