Migrating to use ApplicationContextRunner or ImportAutoConfiguration with SpringApp.run, instead of SpringApplicationBuilder, because builder does not handle AutoConfiguration properly
SimpleTaskAutoConfiguration now has an annotation AutoConfigureBefore the BatchTaskAutoConfig so that it is processed prior. THis is so that that BatchTaskAutoConfig can create the appropriate beans
SimpleTaskAutoConfiguration has new annotations so that it is AutoConfigured after BindingServiceConfiguration and after SimpleTaskAutoConfiguration. This is so that it does not attempt to start emitting messages before stream is ready and it can create the appropriate beans after SimpleTaskAutoConfiguration has run.
Renamed SimpleTaskConfiguration to SimpleTaskAutoConfiguration.
Task version updated to 2.1.0
Added missing headers
Updated documentation.
Deprecated EnableTask
Added ability to disable Task autoconfiguration.
Removed @EnableTask from tests
Resolves#439Resolves#440Resolves#448Resolves#466
Per Stephane's comment on the related issue, Spring Boot starters are
expected to bring in the spring-boot-starter. Before this commit, the
Spring Cloud task starter did not, which lead to incorrect logging
configuration. This commit addresses that issue.
Resolves SCT-359
* Updated spring cloud streams to 1.1.0.RELEASE
* Updated cloud dependencies parent to 1.2.1.RELEASE
* Updated samples to 1.4.1
* Updated Tests to take advantage of 1.4 boot test annotations
* Removed @Bindings as they are deprecated
* Updated BatchApplication test to pass. Boot no longer logs environment values. So count was reduced from 3 to 1
resolves#218, #221
renamed spring-cloud-task-starter to spring-cloud-starter-task
