Will support JobLauncherCommandLineRunner if running task on Boot 2.2.0
resolves#645
Updated based on code review and rebased
Updated code based on code review
All version changes are present.
Fixed all Java-Doc Errors and warnings
* Due to the stricter nature of the javadoc compiler we can't wrap <ul> / <ui> in <p>
* We will also need to Push up a test app for taklauncher to work with. The old one fails to start now. Or use one of the task starters possibly.
* Built on the work from TASK-439C. Wait for that merge before merging this one.
* Replaced applicationFailedEvent class attribute with applicaitonFailedException
* Also polished the app used by the taskLauncherSink integration test
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
This commit adds the ability to configure the order for the
TaskJobLauncherCommandLineRunner. It also provides minor polish on a
few other code review related items.
* cleanup removing unused headers
* Updated asserts in code base that needed messages (marked as deprecated)
* left one test that was testing a deprecated constructor. When that code is removed we can remove that test.
* some other cleanup
resolves#338
This commit adds the TaskExecutionListenerSupport, a no-op
implementation of the TaskExecutionListner. This allows a user to extend
the TaskExecutionListenerSupport and simply override what they need
instead of implementing all of the methods.
resolves#115
* Fixes bug where if the user set the environment variable and commandline args a unique constraint would fire.
* Updated docs
* Removed deprecation
* Fixed version number for integration test.
Added integration tests for externally generated task executions
Add externalExecutionId
resolves#80
This commit adds on an abstraction for the providing unique command line
arugements for each worker. It also updates the partitioned job sample
to be able to successfully be run on CloudFoundry.
Resolvesspring-cloud/spring-cloud-task#193
Updated based on comments
When launching workers as separate tasks, it can be useful to be able to
use additional logic to define environment variables. This commit
provides an abstraction to allow for the customization of environment
variables on a per worker basis as well as two useful implementations:
* A no-op implementation (returns an empty Map).
* An implementation that moves the current environment variable handling
* out of the `DeployerPartitionHandler`.
Resolvesspring-cloud/spring-cloud-task#181
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
