Provide example of successfully running the same job twice in a row
sastafford opened this issue · comments
The problem is when you run a job a second time, the job instance is persisted into the JobRepository. When you run a job the second time, you need to pass in a unique set of JobParameters.
None of the next, restart, abandon commands were being triggered in CommandLineJobRunner. Fixing that as part of this defect.
Fixed in 1.1.0