Julien Ponge
Julien Ponge
Let's consider this. `Flow` has obviously not changed, but there might be a few places in the Mutiny implementation where language and standard library upgrades might be helpful. /cc @heubeck...
The removal of `Future.future()` breaks binary compatibility in the 2 branches.
Along with the _bare_ projects, it would be useful to provide project variants using the (opinionated) Maven and Gradle plugins: * https://github.com/fabric8io/vertx-maven-plugin * https://github.com/jponge/vertx-gradle-plugin
The idea is to add a Mutiny module to produce a reduced jar with shaded dependencies from the main Mutiny artefact. More specifically: - it would not have JPMS `module-info.class`...
Following https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ we need to move the CI/CD of some of the projects to upload to Maven Central instead. At the very least we'll have to: - [ ] create...
Ref: #1577
An operator that generalises the use-cases as in #1595, using: - some gathering state + initial supplier, - some emission predicate, - some state reset action
Mutiny always had a very custom release process. The current one uses: - JReleaser to tag, assemble release notes, and announce them - a job to release to Maven Central....