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
Upgrade to javassist 3.23.1-GA / JDK 11 issue #14610
Comments
Thanks for the report but Spring Boot 2.1, the version that will officially support Java 11, is already using Javassist 3.23.1. |
@juanmbellini also, please consider reviewing Spring Boot with Java 9 and above. |
Hello, I've upgraded my app to Spring Boot 2.1 M4 + Java 11 and I still have the issue :
The workaround suggested by @juanmbellini solves the issue. Have a nice day :) |
@clemstoquart Then you have something in your build configuration that has caused the version of Javassist to be downgraded. Spring Boot does not manage to version of Javassist but it does manage the version of Hibernate. 2.1.0.M4 uses Hibernate 5.3.6.Final and it uses Javassist 3.23.1-GA. If you check your project's dependencies, I suspect that you will see an older version of Javassist being pulled in transitively and Maven will prefer the version that's nearest to the root of the dependency graph. |
Hi @wilkinsona Thanks for your guidance. You were right, I had something wrong with my dependencies. Everything is working well now :) |
Thank you so much this helped me so much thank god for randomly finding it before I banged my head too hard... |
I was having this same issue using JDK 8 as I was using hibernate-envers. This maven import has an exclusion on javassist for its hibernate-core import. The following fixed the issue for me.
|
Thanks so much @juanmbellini , I was trying to solve this for a day now |
Application does not start when using JDK11. It seems that there is a problem with javassist and Hibernate:
Adding the following dependency solves the problem:
Info taken from https://medium.com/criciumadev/its-time-migrating-to-java-11-5eb3868354f9
The text was updated successfully, but these errors were encountered: