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.
- Due to the lack of multipage Html support we need to revert to Docbook for the time being
- Revert "gh-246 Remove docbooks from asciidoctor infrastructure"
- This reverts commit 4ed50a6b31.
The Spring build infrastructure has the capabilities to deploy
documentation automatically that it finds in Artifactory. This commit
creates the required zip archive for that process.
Resolves SCT-78
* 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
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
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
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
This introduces a listener that stores the association between a Spring
Batch job and the task it was executed within.
Resolvesspring-cloud/spring-cloud-task#46
Merge Changes based on code review.
With these changes you can "mvn deploy" on the command line
as long as your local settings.xml has the credentials for
the repo.spring.io repositories.
This is the initial cut of the reference documentation for Spring Cloud
Task.
Resolvesspring-cloud/spring-cloud-task#49
Updates per code review
use mvnw instead of mvn in example
Spring Boot now provides the result of an ExitCodeExceptionMapper via an
event called ExitCodeEvent. This commit takes advantage of this new
event.
Resolvesspring-cloud/spring-cloud-task#48
This change removes the Spring Cloud Task dependency upon a
CommandLineRunner from boot and moves the handling of the task lifecycle
closer to the "edge" of a Spring Boot application.
With this change, now a developer simply adds @EnableTask to their
configuration somewhere and the task lifecycle will be recorded.
Resolvesspring-cloud/spring-cloud-task#39
