-
Notifications
You must be signed in to change notification settings - Fork 38.4k
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
Unify standard and ASM AnnotatedTypeMetadata retention behavior #22886
Comments
@jhoeller any problem with this? Is the current behavior intentional? We have a few tests that fail when I make such a change, but I believe that they have just forgotten to use |
Indeed, this was only ever meant to work with |
Thanks, I'll fix this when I look at #22884 |
philwebb
added a commit
to philwebb/spring-framework
that referenced
this issue
May 4, 2019
Update ASM based metadata readers so that only RetentionPolicy.RUNTIME annotations are exposed. This aligned behavior with the reflection based implementation. Closes spring-projectsgh-22886
philwebb
added a commit
to philwebb/spring-framework
that referenced
this issue
May 6, 2019
Update ASM based metadata readers so that only RetentionPolicy.RUNTIME annotations are exposed. This aligned behavior with the reflection based implementation. Closes spring-projectsgh-22886
philwebb
added a commit
to philwebb/spring-framework
that referenced
this issue
May 6, 2019
Update ASM based metadata readers so that only RetentionPolicy.RUNTIME annotations are exposed. This aligned behavior with the reflection based implementation. Closes spring-projectsgh-22886
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reflection based
AnnotatedTypeMetadata
implementations only support@RetentionPolicy(RetentionPolicy.RUNTIME)
annotations. ASM implementations however currently ignore thevisible
attribute and will read bothRetentionPolicy.CLASS
andRetentionPolicy.RUNTIME
annotations.I would like to unify the two implementations if possible.
The text was updated successfully, but these errors were encountered: