resolves#81
Using LockRegistryLeaderInitiator to do leadership election.
When task is started and singleInstanceEnabled isset to true then we use leader election
to determine if a task needs to be started.
Error Event Name had to be updated
Updated to remove all commons-logging-api dependencies to resolve logging issue.
Updated to handle 2.0.0.M3 Spring Cloud Stream
resovles #347
Changes based on code review
This commit removes the dependency on any Spring Boot starters.
Starters are still used in the test scope, but should not impact the
library's dependencies.
Resolves#294
Created a Spring Boot starter that can be used to configure Spring Cloud
Task and it's related functionality.
Updates per code review
Removed autowiring of app context
Refactored DeployerPartitionHandler to correctly use environment variables
Exposed deployment properties of TaskLauncher
Exposed deployment properties via the TaskLaunchRequest
Updated based on code review
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.
With these changes you can "mvn deploy" on the command line
as long as your local settings.xml has the credentials for
the repo.spring.io repositories.
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
* `DefaultTaskConfigurer` returns only one `SimpleTaskRepository` all others have been removed
* `SimpleTaskRepository` can use `JdbcTaskExecutionDao` or a `MapTaskExecutionDao`
* Add `Jdbc` and Map` `TaskRepositoryFactoryBeans` to support the creation of the correct type of `SimpleTaskRepository`
* `TaskDatabaseInitializer` will initialize a database if a datasource is found and if they have not disabled it using the `spring.task.initialize.enable`
* Add tests
* Added Transaction Support
* Re-add the samples to `pom.xml`
* Samples pom skips install and deploy lifecycle targets.
