In the release process of SCDF, it was identified that Spring Cloud
Deployer had been upgraded to JDK 1.8 which was not desirable at the
given time. As part of the rollback, the deployer implementations
provided remained at 1.8, but the SPI was rolled back to 1.7. This
commit addresses the difference between the different versions as well
as updates the code to use the latest `TaskLauncher` code.
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
* 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#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
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
* Added test for sample and cleanup
* Added skipEventsListener
* Added new message format.
* Added integration tests.
* Updated application.properties to add json content type
resolvesspring-cloud/spring-cloud-task#119
This resolves#126
Use RedisConnectionFactory from RedisTestSupport
Add sub-project for integration tests
- Since there are overlaps with the integration tests and the unit tests running together (using redis binder vs test support binder), it is better to move the integration tests
to a separate sub-project
Little cleanup
Adds a Task Listener that emits the TaskExecution as an event via a
Spring Cloud Stream channel (essentially the listener serves as a SCSt
Source).
Resolvesspring-cloud/spring-cloud-task#11
