Sam Brannen 7557967f9e Stop using explicitly aliased value attribute as @⁠Component name ...

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-34346

2025-02-10 18:21:29 +01:00

..

src

Stop using explicitly aliased value attribute as @⁠Component name

2025-02-10 18:21:29 +01:00

.springBeans

Rename modules {org.springframework.*=>spring-*}

2012-01-31 14:37:10 +01:00

spring-context.gradle

Refine dependencies to fix compilation with Java 23

2025-01-09 16:01:39 +01:00