Deprecating the CommandLineRunnerOrder renaming it to ApplicaitonRunnerOrder
This is to reflect the foundation class of CommandLineRunner which is ApplicationRunner
This commit is contained in:
@@ -209,10 +209,10 @@ can be 1 (the default) or be based on the
|
||||
https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-spring-application.html#boot-features-application-exit[specified
|
||||
`ExitCodeGenerator`])
|
||||
|
||||
This functionality uses a new `CommandLineRunner` that replaces the one provided by Spring
|
||||
This functionality uses a new `ApplicationRunner` that replaces the one provided by Spring
|
||||
Boot. By default, it is configured with the same order. However, if you want to customize
|
||||
the order in which the `CommandLineRunner` is run, you can set its order by setting the
|
||||
`spring.cloud.task.batch.commandLineRunnerOrder` property. To have your task return the
|
||||
the order in which the `ApplicationRunner` is run, you can set its order by setting the
|
||||
`spring.cloud.task.batch.applicationRunnerOrder` property. To have your task return the
|
||||
exit code based on the result of the batch job execution, you need to write your own
|
||||
`CommandLineRunner`.
|
||||
//TODO Great place for a example showing how a custom CommandLineRunner
|
||||
|
||||
Reference in New Issue
Block a user