Skip to content

Backport: Do not consider all @Component instances as @Configuration candidates [SPR-10626] #15254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
spring-projects-issues opened this issue Jun 4, 2013 · 1 comment
Closed

Backport: Do not consider all @Component instances as @Configuration candidates [SPR-10626] #15254

spring-projects-issues opened this issue Jun 4, 2013 · 1 comment
Assignees
@jhoeller
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: declined A suggestion or change that we don't feel we should currently apply

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Jun 4, 2013 •
edited
Loading

Phil Webb opened SPR-10626 and commented

A candidate for backporting?

This issue is a backport sub-task of #15238
@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

I eventually decided against backporting this one since it may have subtle side effects. We're happy to deal with such effects in 4.0 but not in a 3.2.x point release, I'd say, unless there is a compelling benefit to gain.

Juergen

@spring-projects-issues spring-projects-issues added status: declined A suggestion or change that we don't feel we should currently apply in: core Issues in core modules (aop, beans, core, context, expression) labels Jan 11, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhoeller jhoeller

Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jhoeller @spring-projects-issues