-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Error running project with Spring Boot Devtools #14
Comments
project runs without the spring-boot-devtools dependency, looks like an error with other dependencies form Salespoint or Spring |
Removed the Spring Boot Dev Tools as the classloader separation causes Salespoint repositories bootstrap to fail for ones in package scope. The JDK proxy mechanism enforces visibility between classloaders and rejects the creation of the proxy for a type invisible to the current one. This has been reported to the team and has a solution pending.
This unfortunately is a known bug in the Spring Boot Dev Tools in the very corner case of loading a package protected class from a parent classloader. I brought it up with the team already and were looking into the issue. Removed the devtools for now. @SvenSeemann - Any chance you roll the removal out to the individual groups' repositories? |
See st-tu-dresden/kickstart#14 for details.
Should be no problem. I just think about a more generic approach to update all repos in the future... @olivergierke can you update the pom files in kickstarter/videoshop/guestbook, so students have no errors when they try to use one of them for their small prototype |
Kickstart is fixed with the commit for this ticket. Videoshop with the one @AndreasZaschka opened, too. The Guestbook never had it applied as I didn't update it in preparation of the release last week. I'll probably upgrade the Guestbook to show it in the lecture today and craft a Sales 6.2 release in the coming days. |
Couldn't start project with STS (Run As Spring Boot App).
Manually adding a run configuration for maven spring-boot:run solves the problem...
The text was updated successfully, but these errors were encountered: