-
Notifications
You must be signed in to change notification settings - Fork 38.1k
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
JPMS: export to spring.core required #33373
Comments
Hi @xenoterracide, For starters, it's still CGLIB just rather our port of CGLIB which we now maintain. Regarding the exception you've encountered, To avoid that, try As a side note, we don't recommend that a |
for some reason I never considered that, or using statics...
well now I wonder if bytebuddy has the same issue
It does, although I think I prefer the I still don't understand why the |
and why I don't seem to have it with hibernate, which I would think has to accomplish something similar with its magic. |
I think this is just a duplicate of #32671 re-open if you disagree |
This is hopefully just a lack of understanding on how spring "cglib" support is supposed to work (in quotes because it's not cglib anymore right?) or how exactly a reflective access needs
exports
instead of justopens
. Sorry if this isn't simply an understanding problem vs an issue which could be fixed to allow my module to work without adding anexports ... to spring...
Adding this fixes it.
org.springframework:spring-core:6.1.11
The text was updated successfully, but these errors were encountered: