d2bc2530cc
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 #439 Resolves #440 Resolves #448 Resolves #466
= Task Events This is a task application that emits events on a channel named `task-events` == Requirements: * Java 7 or Above == Build: [source,shell,indent=2] ---- $ ./mvnw clean install ---- == Execution: [source,shell,indent=2] ---- $ java -jar target/task-events-1.2.1.RELEASE.jar ---- You can listen for the events on the task-events channel with a Spring Cloud Stream Sink like the log sink using the following: [source,shell,indent=2] ---- $ java -jar <PATH_TO_LOG_SINK_JAR>/log-sink-rabbit-1.0.2.RELEASE.jar --server.port=9090 --spring.cloud.stream.bindings.input.destination=task-events ---- == Dependencies: The task-events sample requires an instance of RabbitMQ to be running.