* Updated spring cloud streams to 1.1.0.RELEASE
* Updated cloud dependencies parent to 1.2.1.RELEASE
* Updated samples to 1.4.1
* Updated Tests to take advantage of 1.4 boot test annotations
* Removed @Bindings as they are deprecated
* Updated BatchApplication test to pass. Boot no longer logs environment values. So count was reduced from 3 to 1
resolves#218, #221
renamed spring-cloud-task-starter to spring-cloud-starter-task
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
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
* We had a discussion on this sometime back and it was decided at that time to keep these type of trims and verification in the Repository.
* Fixed bug where trimming was taking 1 character too many
* Updated ExitMessage maxSize test to verify size
* Added ErrorMessage maxSize Test
* While adding taskExplorer to the test noticed it was missing 2 basic tests and added those as well
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
