Simon Baslé

TODO: - [ ] reactor-core - [ ] reactor-pool - [ ] reactor-addons - [ ] reactor-netty - [ ] reactor-kafka - [ ] reactor-rabbitmq - [ ] reactor-kotlin-extensions -...

For now, let's introduce spotless to deal with copyright headers with an update-on-touch range end year.

This one is interesting. I naively tried to use `` as the method name, but ByteBuddy complaints that: ``` java.lang.IllegalStateException: Cannot catch exception during constructor call for public com.example.ConstructorInitTest$ClassWithThrowingConstructor() ```...

for the constructor, we have to defer a bit because it is not even sure allowBlockingCallsInside can work with constructors due to the aforementioned ByteBuddy limitation... let me split this...

note that this is intended as the issue for constructor support.

### TestSuite points of attention - the `useJUnitJupiter()` configuration method will likely have an hardcoded "latest" version. `useJUnitJupiter($junitVersion)` would be preferable

@garyrussell yeah that could be an intermediate way to improve things in 1.3.x. Let me list a few factoids and constraints: - Micrometer 2.x is around the corner, GA late...

# Choosing an `Automatic-Module-Name` The derived name from the standard Maven naming of the artifacts is in the form `reactor.core`/`reactor.test`/`reactor.netty`, with a few simpler ones like `blockhound`... While this could...

# Split Packages The JPMS enforces that no two modules can export the same package. This is for classes that are directly in said packages, so `reactor.adapter` vs `reactor.adapter.akka` is...

### Module Names Proposal 1 *Rejected* - [ ] reactor-core: - `io.projectreactor.core` - `io.projectreactor.test` - [ ] reactor-addons: - `io.projectreactor.adapter` (exports packages reactor.adapter.akka and reactor.adapter.rxjava, **NOT** reactor.adapter) - `io.projectreactor.extra` -...