SpringBoot JobLauncherApplicationRunner returns a success exit code even when no jobs have been run

JobLauncherApplicationRunner returns a success exit code even when no jobs have been run. fix: Rethrowing exception when NoSuchJobException is caught for non configured jobs. Closes: https://github.com/spring-projects/spring-boot/issues/35940

Comment From: scottfrederick

@itsAkshayDubey Thanks for the PR. As also suggested in the issue comments, it would be better to fail early if any job names are unknown instead of potentially processing some jobs and then failing. Starting in Spring Boot 3.0, some validation is done in a @PostConstruct method of JobLauncherApplicationRunner. Can you make changes to this PR so that this validation of job names is also done in a @PostConstruct method? That would also make it easier to forward-merge the changes to later release branches.

Comment From: itsAkshayDubey

Hi @scottfrederick ,

Added suggested changes, kindly have a look.

Thanks, Akshay

Comment From: snicoll

@itsAkshayDubey thank you for making your first contribution to Spring Boot.