Reactor BOM and legacy (2.x, 1.x)
Latest commit d008329 Sep 20, 2018

Reactor Project

Join the chat at


Starting from 3.0, Reactor is now organized into multiple projects:

Reactor Project

A set of compatible versions for all these projects is curated under a BOM ("Bill of Material").

Using the BOM with Maven

In Maven, you need to import the bom first:


Notice we use the <dependencyManagement> section and the import scope.

Next, add your dependencies to the relevant reactor projects as usual, except without a <version>:


Using the BOM with Gradle

Gradle has no core support for Maven BOMs, but you can use Spring's gradle-dependency-management plugin.

First, apply the plugin from Gradle Plugin Portal (check and change the version if a new one has been released):

plugins {
    id "io.spring.dependency-management" version "1.0.1.RELEASE"

Then use it to import the BOM:

dependencyManagement {
     imports {
          mavenBom "io.projectreactor:reactor-bom:Californium-RELEASE"

Then add a dependency to your project without a version number:

dependencies {
     compile 'io.projectreactor:reactor-core'

BOM Versioning Scheme

The BOM can be imported in Maven, which will provide a set of default artifact versions to use whenever the corresponding dependency is added to a pom without an explicitly provided version.

As the different artifacts versions are not necessarily aligned, the BOM represents a release train with a codename-based versioning scheme: the usual MAJOR.MINOR numbers are replaced by a chemical name from the Periodic Table of Elements, in growing alphabetical order.

The first stable release is simply suffixed with -RELEASE, but the equivalent of patch releases are also possible as "Service Releases", appending the suffix -SR followed by the number of the service release (eg. -SR1, -SR2).

So far, the release trains are named:

  • Aluminium for the 3.0.x generation of Reactor-Core (💡)
  • Bismuth for the 3.1.x generation (💡)
  • Californium for the 3.2.x generation (💡)


Join the initiative, fork, discuss and PR anytime. Roadmap is collaborative and we do enjoy new ideas, simplifications, doc, feedback, and, did we mention feedback already ;) ? As any other open source project, you are the hero, Reactor is only useful because of you and we can't wait to see your pull request mate !

GitHub forks license


Community / Support

  • Join the chat at
  • GitHub issues
  • Twitter URL

Detail of Projects

Reactor Core

Reactor Core

Reactive foundations for apps and frameworks and reactive extensions inspired API with Mono (1 element) and Flux (n elements) types

Reactor Netty

Reactor Netty

TCP and HTTP client and server.

Reactor Addons

Reactor Addons

Extra projects adding features to reactor:

  • reactor-adapter: adapt to/from various libraries, mainly RxJava 2.
  • reactor-extra: Retry utils, Math utils, ...
  • reactor-logback: logback adapter for Flux/Mono log() feature.

Snapshot Artifacts

While Stable Releases are synchronized with Maven Central, fresh snapshot and milestone artifacts are provided in the repositories.

To add this repo to your Maven build, add it to the <repositories> section like the following:

	    <name>Spring Snapshot Repository</name>

To add it to your Gradle build, use the repositories configuration like this:

repositories {
	maven { url '' }

You should then be able to import a BUILD-SNAPSHOT version of the BOM, like Californium-BUILD-SNAPSHOT.

Reactive Streams Commons

In a continuous mission to design the most efficient concurrency operators for Reactive Streams, a common effort -codename Reactive Streams Commons- has begun. Reactor is fully aligned with RSC design and is directly inlining RSC within its stable API contract scoped under reactor-core. Reactive Streams Commons is a research effort shared with everyone and is demanding of efficient stream processing challengers, therefore it is naturally decoupled of any framework noise.

Sponsored by Pivotal