Currently our loader classes are in the org.springframework.boot.loader package but they'd really be better in a dedicated org.springframework.boot.loader.launch package, especially if we want to make future changes to the code. We should be able to create new classes that call the existing ones without too much difficulty.
Comment From: steklopod
@philwebb I faced with the error after update to Spring Boot 3.2.0.
I have
ENTRYPOINT ["java", "org.springframework.boot.loader.JarLauncher"]
So update to
ENTRYPOINT ["java", "org.springframework.boot.loader.launch.JarLauncher"]
solved the problem.
But there is no info in internet about it
Comment From: wilkinsona
The change is described in the release notes for Spring Boot 3.2.