Reinstate support for legacy JSR-250 `@javax.annotation.ManagedBean` and JSR-330 `@javax.inject.Named` annotations

[sbrannen]

With the migration to Jakarta annotations in 6.0, we switched to supporting @jakarta.annotation.ManagedBean and @jakarta.inject.Named annotations for component scanning and component name lookups.

To better assist projects in the migration to Spring 6+, we should reinstate support for the legacy JSR-250 @javax.annotation.ManagedBean and JSR-330 @javax.inject.Named annotations so that existing compiled code will continue to work as expected.

Related Issues

• Retain support for legacy JSR-250 javax.annotation.PostConstruct/PreDestroy and JSR-330 javax.inject.Inject in addition to Jakarta EE 9 annotations #27444
• Reinstate dependency injection support for legacy JSR-250 @javax.annotation.Resource annotation #30695

Deliverables

• Support @javax.annotation.ManagedBean and @javax.inject.Named in ClassPathScanningCandidateComponentProvider#registerDefaultFilters(...).
• Support @javax.annotation.ManagedBean and @javax.inject.Named in AnnotationBeanNameGenerator#isStereotypeWithNameValue(...).
• Update tests.
• Update Javadoc.

[sbrannen]

Current work on this feature can be viewed in the following feature branch: main...sbrannen:spring-framework:issues/gh-31090-legacy-ManagedBean-and-Named-annotations

[YSavanier]

Hello.

This is again broken in version 7 :

949432c

What's the purpose of breaking backward compatibility every 5 months...

[bclozel]

@YSavanier please create a new issue.