From 08ddb59f92cc9784a3b7011efb90399fab4e65e5 Mon Sep 17 00:00:00 2001 From: Nishant Raut Date: Sat, 3 Nov 2018 21:35:38 +0530 Subject: [PATCH] Update documentation to remind how JobParameters should be specified See gh-15081 --- .../spring-boot-docs/src/main/asciidoc/howto.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc index 524aa3b017..0902cebd36 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc @@ -2378,6 +2378,8 @@ By default, it executes *all* `Jobs` in the application context on startup (see for details). You can narrow down to a specific job or jobs by specifying `spring.batch.job.names` (which takes a comma-separated list of job name patterns). +Unlike command line option arguments (which starts with `--`, e.g. `--spring=batch`) job parameters has to be passed without dashes to job (e.g. `spring=batch`). + If the application context includes a `JobRegistry`, the jobs in `spring.batch.job.names` are looked up in the registry instead of being autowired from the context. This is a common pattern with more complex systems, where multiple jobs are