* Reverting to snapshot to fix build with spring-functions-catalog 5.0.0-M2
* Fix redis-sink and updated dependencies.
* Added commons-codec for test support.
* Remove tests when Spring Functions Catalog performs exact same test.
* Fix xmpp-sink test dependencies.
Prior to this commit, each app documented its available config props
in its README.adoc. Now that the functions have been moved to the
function catalog, these inline docs are replaced w/ a link to the
respective function catalog docs.
See #524
* Remove `functions` module
* Remove `functions` from build scripts
* Change internal `functions` mentioning in the docs to the dedication Spring Functions Catalog project
* Remove all the TensorFlow modules
* Change to `spring-functions-catalog-bom`
* Update READMEs using `quick-compile.sh`
* Upgrade to Spring Integration AWS `3.0.1`
* Upgrade to Spring Cloud AWS `3.0.1`
* Use `spring-cloud-aws-dependencies` BOM to manage Spring Cloud AWS deps, as well as AWS SDK
* Remove `AmazonS3Properties` in favor of similar properties in the Spring Cloud AWS auto-configuration
* Remove `CompatibleStorageAmazonS3Configuration` in favor of its code migration to the single `AmazonS3Configuration`
* Fix `supplier`, `consumer`, `source` and `sink` for S3 to use API and programing model from the mentioned upgrades
* Add extra `dataflow-configuration-metadata` entries for the mentioned properties from the Spring Cloud AWS auto-configuration
* Regenerate README for `s3-source` and `s3-sink`
* Fix `metadata-store-common` to use the latest Spring Integration AWS for DynamoDB store impl
* * Fix `AmazonS3ConfigurationTests` for missed `AwsAutoConfiguration`
in an `ApplicationContextRunner` setup
* * Remove unused import in the `MetadataStoreAutoConfigurationTests`
* * Remove unused import in the `AbstractAwsS3ConsumerMockTests`
This commit removes all legacy config props metadata files
named `dataflow-configuration-metadata-whitelist.properties`.
This is safe with respect to SCDF because stream apps 4.x
require SCDF 2.11.x to launch the apps. Therefore, no existing
SCDF customers on an older SCDF version (that only supports
the legacy file) will be impacted - the users will all be on
the latest version of SCDF.
Fixes#252
* Renamed spring-configuration-metadata-whitelist.properties (removed "-whitelist")
* Renamed spring-configuration-metadata.properties to
dataflow-configuration-metadata.properties
* Fix rsocket
* Rsocket props now added back in
* Rename rsocket-sink metadate file to non-legacy format
Fixes https://github.com/spring-cloud/stream-applications/issues/368
* Upgrade to `spring-cloud-aws-2.4.2`; fix respective package changes
* Remove `AutoConfigurationExclusionEnvironmentPostProcessor` since classes in the SC-AWS
are not considered as auto-configuration anymore.
Instead, add an explicit `@Import` into `AmazonS3Configuration`.
Not sure, though, why it was excluded before at all
* Fix `MetadataStoreAutoConfigurationTests` with the current state of code.
Looks like before it was designed for auto-configuration based on classpath content
* Re-enable other AWS S3 tests
This fix has helped to spot a bug in Spring Integration Testing framework:
e2d8eeb04d
Co-authored-by: Chris Bono <cbono@vmware.com>
This proposal fixes many build warnings and is a general cleanup of the pom.xml files.
* Remove duplicate `dependency` entries from pom.xml files
* Remove duplicate `repository` entries from pom.xml files
* Replace deprecated use of `receive(long)` in `HttpSourceTests`
* Reduce logging for Twitter integration tests
Fixes#271
