To provide the ability to control task orchestration via the exit
message, we moved the stack trace storage to a new field. This means
that exit message is now a field we can use similar to how exit code is
in batch, and still have the stack trace of an unsuccessful task
execution stored.
Resolvesspring-cloud/spring-cloud-task#186
Disabled integration tests by default
Just some cleanup on merge
This commit upgraded all places where Spring Cloud Task explicitly
references Spring Boot 1.4
Resolvesspring-cloud/spring-cloud-task#166
Updated the jar version numbers in the adocs to 1.1.0
resolves#174
Added H2 dependency and fixed BatchExecutionEventTest to use SimpleTaskConfigurationClass
Check Task Repo to determine if task was launched successfully
H2 now uses a random port
Now uses TaskExplorer
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
* Update pom to include text for contributor agreement
* Update samples to the latest release number
* Remove CLA section from README.adoc
Resolves#172
Reset the ResourceLoader to DeploymentResourceLoader
Adjusted the poms to not run deploy for Samples as well as integration tests
Used default constructor
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
Versions where updated in documentation that is included in the
generation of our reference documentation.
Also, to clean up version management within the samples, the
spring-cloud-task-dependencies was introduced into each pom so that
versions are managed at that level.
Versions where updated in documentation that is included in the
generation of our reference documentation.
Also, to clean up version management within the samples, the
spring-cloud-task-dependencies was introduced into each pom so that
versions are managed at that level.
Updated a version number
