Skip to content

Update documentation to remind how JobParameters should be specified #15081

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Update documentation to remind how JobParameters should be specified #15081

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
27bd128
Merge pull request #1 from spring-projects/master
nishantraut Nov 3, 2018
aeea5a2
10689 JobParameters arguments documentation
nishantraut Nov 3, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2456,6 +2456,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
Expand Down