Per Stephane's comment on the related issue, Spring Boot starters are
expected to bring in the spring-boot-starter. Before this commit, the
Spring Cloud task starter did not, which lead to incorrect logging
configuration. This commit addresses that issue.
Resolves SCT-359
* 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
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
The 2.0 PR merge missed a couple items that broke the build.
Specifically the maven plugin repository was not specified so the
snapshots for the Spring Boot Maven Plugin could not be found. Also the
ordering of the parameters in the Hibernate generated SQL was different
so the JpaApplicationTests were failing.
* 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
