Skip to content

Make naming of @Configuration class processing-related artifacts consistent [SPR-5600] #10271

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
spring-projects-issues opened this issue Mar 22, 2009 · 1 comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Chris Beams opened SPR-5600 and commented

AbstractConfigurationClassProcessor -> AbstractConfigurationClassPostProcessor
ConfigurationEnhancer -> ConfigurationClassEnhancer
ConfigurationParser -> ConfigurationClassParser

Also update corresponding unit test class names to match


Attachments:

Referenced from: commits cc713ad

@spring-projects-issues
Copy link
Collaborator Author

Chris Beams commented

Done, however AbstractConfigurationClassProcessor has not been renamed to *PostProcessor, as it could technically be used in any processing context, not just a post-processing context. That's up to the concrete implementations to decide.

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: core Issues in core modules (aop, beans, core, context, expression) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 M3 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant