Sam Brannen 17a94fb110 Improve warning for unexpected use of value attribute as @⁠Component name ...

Prior to this commit, if a String 'value' attribute of an annotation
was annotated with @⁠AliasFor and explicitly configured to alias an
attribute other than @⁠Component.value, the value was still used as the
@⁠Component name, but the warning message that was logged stated that
the 'value' attribute should be annotated with
@⁠AliasFor(annotation=Component.class). However, it is not possible to
annotate an annotation attribute twice with @⁠AliasFor.

To address that, this commit revises the logic in
AnnotationBeanNameGenerator so that it issues a log message similar to
the following in such scenarios.

WARN o.s.c.a.AnnotationBeanNameGenerator - Although the 'value'
attribute in @⁠example.MyStereotype declares @⁠AliasFor for an
attribute other than @⁠Component's 'value' attribute, the value is
still used as the @⁠Component name based on convention. As of Spring
Framework 7.0, such a 'value' attribute will no longer be used as the
@⁠Component name.

See gh-34346
Closes gh-34317

2025-02-10 13:29:40 +01:00

..

src

Improve warning for unexpected use of value attribute as @⁠Component name

2025-02-10 13:29:40 +01:00

.springBeans

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

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

spring-context.gradle

Add ThreadLocalAccessor for LocaleContext and RequestAttributes

2024-02-15 15:49:55 +01:00