This is so they can be updated in a minimal amount of places and leverage the maven hierarchy to propagate them where appropriate.
While working with SNAPSHOT releases of Spring Boot, Spring Integration, and Spring Cloud, it required touching every pom.xml file
in order to reflect the use of the SNAPSHOT. After this change, it will only be required to change the property in the top
functions pom.xml and the versions will reflect to all submodules.
Maven introduced the ability use a key property, revision to propagate this information to the <parent> declarations in each pom.
This was enabled in Maven 3.5+
https://maven.apache.org/maven-ci-friendly.html
* This RSocket consumer is using the fire-and-forget strategy of execution.
* Generating the corresponding sink.
* Addressing the original PR review comments from
https://github.com/spring-cloud/stream-applications/pull/116
* Addressing PR review comments
* Fix README
* Addressing PR review
* Have all the required dependencies in class path which give us a `MessageGroupStore` implementation
* Disable all their auto-configurations in the `ExcludeStoresAutoConfigurationEnvironmentPostProcessor`
* Enable only those which are configured by the `aggregator.messageStoreType` property
* Implement a fully reactive function around an aggregator making an interaction via a pair of `FluxMessageChannel`
* Fix checkstyle issues
* Change the app generator maven plugin to new coordinates
- Add supplier, source and boot auto-config.
- Add work around for KafkaNull handling.
- Update CDC to 1.2.1.Final. Replace the deprecated properties.
remove comments
Add missing metadata configuration. Improve README docs.
CDC: add all metadata for doc auto-generation
Remove custom KafkaNullConverter.
- The fixed KafkaNullConverter implementation comes with kafka binder 3.0.8-BUILD-SNAPSHOT or newer.
Add repositories to maven config in app generation project.
Remove the unnecessary function version in maven plugin configuration for app generation.
