From 5393962685ea9d6005300b9f08570f81ab9448b4 Mon Sep 17 00:00:00 2001 From: Michael Minella Date: Mon, 27 Jun 2016 15:26:42 -0500 Subject: [PATCH] Fixed verbage around return codes and batch --- spring-cloud-task-docs/src/main/asciidoc/batch.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-cloud-task-docs/src/main/asciidoc/batch.adoc b/spring-cloud-task-docs/src/main/asciidoc/batch.adoc index 61471921..457fa282 100644 --- a/spring-cloud-task-docs/src/main/asciidoc/batch.adoc +++ b/spring-cloud-task-docs/src/main/asciidoc/batch.adoc @@ -113,7 +113,7 @@ is covered in detail in the section As discussed before Spring Cloud Task applications support the ability to record the exit code of a task execution. However in cases where a user is running a Spring Batch Job within a task, regardless of how the Batch Job -Execution completes the result of the task will always be zero when using a CommandLineRunner for example. Keep in mind +Execution completes the result of the task will always be zero when using default Batch/Boot behavior. Keep in mind that a task is a boot application and the exit code returned from the task is the same as a boot application. So to have your task return the exit code based on the result of the batch job execution, you will need to write your own CommandLineRunner.