You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on #20609, we should also apply the same policy to superclass methods, even if annotation inheritance expectations across generics might be less common there.
Due to the inconsistency with generic interfaces and the inconsistency between AnnotationUtils and AnnotatedElementUtils (since only the former finds annotations on generic interface methods), this qualifies as a follow-up bug that needs to be fixed in the 5.0.x line as well.
Juergen Hoeller opened SPR-17146 and commented
Following up on #20609, we should also apply the same policy to superclass methods, even if annotation inheritance expectations across generics might be less common there.
Due to the inconsistency with generic interfaces and the inconsistency between
AnnotationUtils
andAnnotatedElementUtils
(since only the former finds annotations on generic interface methods), this qualifies as a follow-up bug that needs to be fixed in the 5.0.x line as well.Affects: 5.0.8, 5.1 RC1
Issue Links:
Referenced from: commits 4521a79, 688ef9a
The text was updated successfully, but these errors were encountered: