In testing and other use cases, the ability to keep a context open
beyond the end of a task can be useful. This change provides the
ability to keep the context alive once a task has completed while also
explicitly shutting the context down (by default) once a task has ended.
Resolvesspring-cloud/spring-cloud-task#102
This introduces a listener that stores the association between a Spring
Batch job and the task it was executed within.
Resolvesspring-cloud/spring-cloud-task#46
Merge Changes based on code review.
This PR removes the use of SLF4J from all non-test code. SLF4J is still
directly referenced in the unit tests because of the mocking
functionality we're using. We can explore refactoring that in a later
PR.
Resolvesspring-cloud/spring-cloud-task#101
TaskNameResolver allows the ability to customize how a task is named.
During normal use cases, the provided SimpleTaskNameResolver should
suffice.
resolvesspring-cloud/spring-cloud-task#54
This change removes the Spring Cloud Task dependency upon a
CommandLineRunner from boot and moves the handling of the task lifecycle
closer to the "edge" of a Spring Boot application.
With this change, now a developer simply adds @EnableTask to their
configuration somewhere and the task lifecycle will be recorded.
Resolvesspring-cloud/spring-cloud-task#39
* Timestamp Demonstrates a Spring boot/task application as a single java file.
* HelloWorld Demonstrates a Spring boot/task application using java configuration.
resolvesspring-cloud/spring-cloud-task#23