Browse Source
Prior to this commit, if a custom stereotype annotation was meta-annotated with @Component and declared a local String `value` attribute that was explicitly configured (via @AliasFor) as an override for an attribute other than @Component.value, the local `value` attribute was still used as a convention-based override for @Component.value. Consequently, a local `value` attribute was used as a custom @Component name, even when that is clearly not the intent. To address that, this commit revises the logic in AnnotationBeanNameGenerator so that a `value` attribute which is explicitly aliased to something other than @Component.value is no longer used as an explicit @Component name. See gh-34317 Closes gh-34346pull/34399/head
2 changed files with 12 additions and 25 deletions
Loading…
Reference in new issue