Skip to content

Improve handling of multiple @EnableAutoConfiguration annotations with different excludes #2939

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.

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

Closed
wilkinsona opened this issue May 12, 2015 · 0 comments
Labels
status: declined A suggestion or change that we don't feel we should currently apply

Comments

@wilkinsona
Copy link
Member

If you use @EnableAutoConfiguration multiple times in your application each is processed in isolation. This can cause confusion with excludes as they must be configured on every occurrence of @EnableAutoConfiguration to take effect.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Nov 30, 2015
@wilkinsona wilkinsona removed the status: waiting-for-triage An issue we've not yet triaged label Nov 30, 2015
@wilkinsona wilkinsona added for: team-attention An issue we'd like other members of the team to review priority: normal type: enhancement A general enhancement labels Jan 12, 2017
@philwebb philwebb added status: declined A suggestion or change that we don't feel we should currently apply and removed for: team-attention An issue we'd like other members of the team to review priority: normal type: enhancement A general enhancement labels Feb 2, 2017
@philwebb philwebb closed this as completed Feb 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Development

No branches or pull requests

3 participants